Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol __extension__', error msg

2009-07-09 Thread Tom Tromey
Larry == Larry Evans cppljev...@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

avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol __extension__', error msg

2009-07-08 Thread Larry Evans
I compiled gcc with -g3 -O0' compiler flags to enable invocation of macros during a gdb session; however, the macro, PACK_EXPANSION_PATTERN, apparently uses a symbol: __extension__ not understood by gdb. How can gdb be made to understand __extension__ or how can __extension__ be rm'ed from

Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol __extension__', error msg

2009-07-08 Thread Richard Henderson
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

Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol __extension__', error msg

2009-07-08 Thread Daniel Jacobowitz
On Wed, Jul 08, 2009 at 03:14:20PM -0700, Richard Henderson wrote: 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

Re: avoiding gdb cc1plus PACK_EXPANSION_PATTERN(result) gives 'No symbol __extension__', error msg

2009-07-08 Thread Ian Lance Taylor
Richard Henderson r...@redhat.com writes: 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