This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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: RFC: C/C++ preprocessor macro support for GDB

From: Jim Blandy <jimb at redhat dot com>
To: Neil Booth <neil at daikokuya dot demon dot co dot uk>
Cc: gdb-patches at sources dot redhat dot com, gcc at gcc dot gnu dot org
Date: 18 Mar 2002 23:33:17 -0500
Subject: Re: RFC: C/C++ preprocessor macro support for GDB
References: <20020317062306.CC96D5E9DE@zwingli.cygnus.com><20020318183339.GB19897@daikokuya.demon.co.uk>


Instead of the bug you guessed, here's the bug I actually do have:

(gdb) show macro A
Defined at /home/jimb/gdb/macros/play/test.c:12
#define A(x) x
(gdb) show macro B
Defined at /home/jimb/gdb/macros/play/test.c:12
#define B(x) A
(gdb) macro expand B(ignored)(passed through)
expands to: A(passed through)
(gdb) 

ISO/IEC 9899:1999(E) 6.10.3.4 para 1: "Then, the resulting
preprocessing token sequence is rescanned, along with all subsequent
preprocessing tokens of the source file, for more macro names to
replace."  It's the "along with all subsequent PP tokens" part that I
got wrong.

(Did I mention that I think we should replace macroexp.c with libcpp?)

References:
- RFC: C/C++ preprocessor macro support for GDB
  - From: Jim Blandy
- Re: RFC: C/C++ preprocessor macro support for GDB
  - From: Neil Booth

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