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: Richard Henderson <rth at redhat dot com>
- To: Larry Evans <cppljevans at suddenlink dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 08 Jul 2009 15:14:20 -0700
- Subject: Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol "__extension__"', error msg
- References: <h334g5$ij2$1@ger.gmane.org>
On 07/08/2009 03:11 PM, Larry Evans wrote:
It would be much easier if gdb understood __extension__. Is there a way?
In this case, no. It's protecting a statement expression, which gdb
will never be able to parse.
A better project for helping debug gcc would be to convert all macros
that use statement expressions into proper inline functions. Which
would then be emitted as out-of-line functions by gcc's -fkeep-inlines
flag, which would yield something that's callable from within gdb.
r~