Re: evaluating #defines in gdb?

From: Mark Coletti (
Date: 11/03/95

Trey T. Morita pounded furiously on the keyboard:

> On Thu, 2 Nov 1995, Mark Devlin wrote:
> > gdb (and other source-level debuggers) get the info about variables from 
> > the symbol table in the executable.  When you compile with debug info, 


> Thanks for the info Mark, but the part that got clipped (the original 
> mail by me) was using an example of GET_STR(ch) which is in actuality . . 

> #define GET_STR(ch)     ((ch)->aff_abils.str)

> There's no real way to sub a const declaration for this, now, is there?

	Well, it's not a total loss if you're using gcc and gdb;
apparently gcc supports a -ggdb# where # specifies the level of
debugging information you want added to the generated binaries.  The
highest level, 3, _supposedly_ groks macro definitions, too.  But,
I've never tried this, so I don't know how well this works, if it does
at all.  YMMV!  =8-)

Mark Coletti                       |  DBA Systems, Inc.  Fairfax, VA                 |  United States Geological Survey  |  Office of Standards & Technology
                  I never buy books on impulse. Only on warp.

This archive was generated by hypermail 2b30 : 12/07/00 PST