This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: Debugging Macros

From: "Tom Browder" <tom dot browder at gmail dot com>
To: "Andrew Haley" <aph at redhat dot com>
Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Wed, 23 Jan 2008 06:25:19 -0600
Subject: Re: Debugging Macros
References: <8bc817ee0801230409g1c9da085g933e2fbfd7404b30@mail.gmail.com> <47972F71.4080007@redhat.com>

On Jan 23, 2008 6:13 AM, Andrew Haley <aph@redhat.com> wrote:
> Tom Browder wrote:
...
> > Is there an easy way (such as defining an environment variable in the
> > build environment) to get the gcc build system to show the
> > preprocessed code to help backtrack the problem?
...
> Set your CC when running make: "make CC='gcc -g -save-temps -Wp,-dD ...'
>
> This will give you all macro definitions, expanded in .i files.
>
> For extra credit, run the .i files through GNU indent.

Thanks, Andrew.

-Tom

References:
- Debugging Macros
  - From: Tom Browder
- Re: Debugging Macros
  - From: Andrew Haley

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