This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol "__extension__"', error msg
- From: Tom Tromey <tromey at redhat dot com>
- To: Larry Evans <cppljevans at suddenlink dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 09 Jul 2009 10:16:05 -0600
- Subject: Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol "__extension__"', error msg
- References: <h334g5$ij2$1@ger.gmane.org>
- Reply-to: tromey at redhat dot com
>>>>> "Larry" == Larry Evans <cppljevans@suddenlink.net> writes:
Larry> I compiled gcc with -g3 -O0' compiler flags to enable invocation of
Larry> macros during a gdb session; however, the
Larry> macro, PACK_EXPANSION_PATTERN, apparently uses a symbol:
Larry> __extension__
Larry> not understood by gdb. How can gdb be made to understand
Larry> __extension__ or how can __extension__ be rm'ed from the
Larry> macros?
This is a gdb PR:
http://sourceware.org/bugzilla/show_bug.cgi?id=9748
If you use a new (CVS) gdb, that has "macro define", you can use the
defines in that PR to circumvent the GCC statement expressions and
make everything work reasonably well. You lose checking but I never
missed that when evaluating things from the gdb CLI.
Once this gdb is released I think those macro defines should go in
gcc's .gdbinit.
Tom