Open FunkyFr3sh opened 4 months ago
Actually, this bug is not related to NASM at all. It's related to the .patch section that is being added. Luckily in this case the section is only a temporary one and can be removed via objcopy
.
Not sure if any changes are needed to cv2pdb to maybe improve the compatibility with such corner cases? I'll keep the issue open for now though. For me the problem is solved, feel free to close the issue if needed
When one of the source files is built via NASM cv2pdb fails to remove the COFF_SYMBOLS from the built executable.
I tried to create a minimal version to reproduce the bug, it should build fine with w64devkit: nasm.zip no-nasm.zip
test exe (before cv2pdb): test1.exe.zip
Without NASM source file Before cv2pdb:![image](https://github.com/rainers/cv2pdb/assets/8355237/5a87911e-14f1-4d2f-8cb5-acac2248ab95)
After cv2pdb:![image](https://github.com/rainers/cv2pdb/assets/8355237/d8475301-6b62-4243-a7f2-4a49dc33f214)
With NASM source file Before cv2pdb:![image](https://github.com/rainers/cv2pdb/assets/8355237/82dea78b-f03c-47ea-809d-6b67d0708098)
After cv2pdb:![image](https://github.com/rainers/cv2pdb/assets/8355237/10a908bb-dbe0-425a-ab8e-9a0f83242bcb)