support for DWARF extensions used by GCC 4.7?

support for DWARF extensions used by GCC 4.7?

[Nathan Ridge]

Hi,

The following in stated on the GCC website [1]:

"GCC now supports various new GNU extensions to the DWARF debugging 
information format, like entry value and call site information, typed 
DWARF stack or a more compact macro representation.  Support for these 
extensions will come in GDB 7.4. They can be disabled through the
    -gstrict-dwarf command-line option."

Has this support been added to GDB trunk?

I ask because I am trying to debug a program built with GCC trunk,
with GDB trunk, and I am experiencing all sorts of weird behaviour
(breakpoints being ignored, no line number given when a breakpoint
is reached, inability to step into functions) that is usually
indicative of the generated debug info format and the format expected
by the debugger not being in sync.

On the other hand, adding -gstrict-dwarf when compiling does not
help, so it may be a different issue...

Thanks,
Nate


[1] http://gcc.gnu.org/gcc-4.7/changes.html
 		 	   		  

Re: support for DWARF extensions used by GCC 4.7?

[Tom Tromey]

>>>>> "Nathan" == Nathan Ridge <zeratul976@hotmail.com> writes:

Nathan> "GCC now supports various new GNU extensions to the DWARF debugging 
Nathan> information format, like entry value and call site information, typed 
Nathan> DWARF stack or a more compact macro representation.  Support for these 
Nathan> extensions will come in GDB 7.4. They can be disabled through the
Nathan>     -gstrict-dwarf command-line option."

Nathan> Has this support been added to GDB trunk?

Yes.

Nathan> I ask because I am trying to debug a program built with GCC trunk,
Nathan> with GDB trunk, and I am experiencing all sorts of weird behaviour
Nathan> (breakpoints being ignored, no line number given when a breakpoint
Nathan> is reached, inability to step into functions) that is usually
Nathan> indicative of the generated debug info format and the format expected
Nathan> by the debugger not being in sync.

Nathan> On the other hand, adding -gstrict-dwarf when compiling does not
Nathan> help, so it may be a different issue...

Yeah, probably so.  If you have reasonably easy ways to reproduce the
bugs, we're interested -- file in bugzilla.

Tom