Mail Archives: djgpp-workers/2012/12/13/14:57:59
Am 13.12.2012 20:10, schrieb Juan Manuel Guerrero:
> Am 13.12.2012 18:57, schrieb Eli Zaretskii:
>>> Date: Thu, 13 Dec 2012 01:15:38 +0100
>>> From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
>>> CC: djgpp-workers AT delorie DOT com
>>>
>>> > Also, does objdump succeed to show line number info in a.exe?
>>> No. objdump is not able to read neither line numbers nor inserted source code lines.
>> Does objdump succeed to show line numbers in temacs.exe or emacs.exe?
>>
>> If it works in temacs, then I'm stumped: after all, temacs.exe is just
>> a normal C program, like any other one. Perhaps the size of a program
>> makes a difference?
>>
> The only objdump program that is able to display line numbers and/or
> code lines when the sources have been compiled with -gcoff is the one
> from bnu217b. Starting with bnu219b and later are no longer able to
> display neither line numbers nor code lines. Only assembler code is
> displayed. Of course, for those portions of the binary that contains
> library code like printf or crt1.S all versions display line numbers and
> code lines.
>
> Regards,
> Juan M. Guerrero
>
Sorry, only to clarify the issue. I have tried to read line numbers from both
temacs and emacs but this is only possible if and objdump program is used
from bnu217 or previous versions. As soon as objdump programs from
bnu219 or later versions are used, it is no longer possible to show debug
info like line numbers if the binary has been compiled with -gcoff.
This shows that the coff debug support is seriously broken.
Regards,
Juan M. Guerrero
- Raw text -