You are not logged in.
- Topics: Active | Unanswered
#1 2017-11-13 12:25:25
Can't debug on FPC as win64 target because of crc32c64.obj
The problem is in crc32c64.obj - during linking on FPC for Win64 targer we got a Warning: Object file "crc32c64.obj" contains 32-bit absolute relocation to symbol ".debug_info". After this debugging fail with Dwarf Error: bad offset (0x1cc5a70) in compilation unit header (offset 0x7b76a4 + 6)
Where we can get a sources for crc32c64.obj and compilation parameters? We will try to recompile...
Offline
#2 2017-11-13 12:41:05
Re: Can't debug on FPC as win64 target because of crc32c64.obj
I've no problem here with latest FPC trunk.
Try to change the following line 3763 to disable this external link (which makes a huge performance boost, but perhaps not mandatory for you):
{..$define CRC32C_X64} // external crc32_iscsi_01 for win64/lin64The sources are from Intel itself.
See e.g. https://www.intel.com/content/dam/www/p … -paper.pdf and the associated source.
Offline
#3 2017-11-14 13:41:35
- ssoftpro
- Member
- Registered: 2017-11-14
- Posts: 7
Re: Can't debug on FPC as win64 target because of crc32c64.obj
Hi, ab! I've managed to strip debug information from crc32c64.obj and this allows me to compile and debug using fpc in Win64 without problems. Where would it be better to put the file with debug info stripped? should I place it in the fpc-win64 folder or it is better to just replace the current version of crc32c64.obj?
Offline
#5 2017-11-15 12:28:45
Re: Can't debug on FPC as win64 target because of crc32c64.obj
We stripped a debug information from crc32c64.obj using linux command "strip --strip-debug" and committed a new file - see [2c4bafb632]. Now debugger work in FPC/Win64 and file became 2,5 Kb less
Offline