This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [vta->trunk] VTA merge


On Thu, Sep 03, 2009 at 06:16:30PM -0700, Mark Mitchell wrote:
> Tom Tromey wrote:
> 
> > I don't know about other debuggers, but GDB will issue an error like:
> > 
> >     Unhandled dwarf expression opcode 0x9e
> > 
> > if you try to print a variable whose location uses that opcode.
> 
> That's unfortunate.  Obviously, we can't do anything about older
> versions of GDB, but can we change GDB so that it doesn't complain and
> just silently ignores the expression, unless in some debugging mode?  If
> I'm a user, and I have some compiler that spits out weird DWARF GDB
> doesn't understand, scary messages aren't helping me.

Yes, it is unfortunate.  But we can't retroactively change released GDBs,
and the upcoming GDB will understand it.  And you need the upcoming GDB to
debug GCC 4.5 compiled code anyway, because older GDBs mishandle
DW_CFA_restore_state which is now used all around in .eh_frame, otherwise
backtraces really don't work.

	Jakub


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]