Re: [Mingw-users] what type of debugging information mingw is using

[Tor L. <tm...@ik...>]

> The gdb command 'info source' should indicate which is used.

Also, running size -A or link.exe -dump -headers on an executable will
tell you what sections are present. If you see sections named .stabs
and .stabstr, that indicates the presence of stabs debugging
information. If you see sections named .debug_line etc, that means
dwarf2. If you see a section called .debug, that is dwarf1 I think,
and .eh_frame would indicate dwarf3. (This is not 100% clear to me,
just my impression based on some code I see in a program that attempts
to handle these sections.)

Note that there might also be a .gnu_debuglink section, then the
actual debug information (one (or several) of the above) is in a
separate file named in the .gnu_debuglink section.

And if you in a objdump -p output see that there is a "Debug
Directory" present, and some tool like peview shows you that the
directory in question contains information of type
"IMAGE_DEBUG_TYPE_CODEVIEW", then there is a pointer to external
Microsoft style debugging (.pdb file). peview will also show you what
the name of the .pdb file is.

--tml