From: jreiver@free.fr
To: Robert Dewar <dewar@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: how to examine data with compiler optimization option set?
Date: Tue, 02 Sep 2008 21:45:00 -0000 [thread overview]
Message-ID: <1220391632.48bdb2d04bfd7@imp.free.fr> (raw)
In-Reply-To: <48BDB1B0.4040703@adacore.com>
Yes, I knew that the optimization option removes the visibility for a, b and c.
But GDB user manual seemed to say that you can still view them with providing
-gstabs or -gdwarf2 option, in addition to the -O[1|2|3] option you might want
to keep.
Isn't that possible at all? (I am currently evaluating the debugging facilities
of gdb)
Regards,
J R
Quoting Robert Dewar <dewar@adacore.com>:
> J R wrote:
> > Extract of GDB user manual:
> >
> > "Another possible effect of compiler optimizations is to optimize unused
> > variables out of existence, or assign variables to registers (as opposed to
> > memory addresses). Depending on the support for such cases offered by the
> debug
> > info format used by the compiler, GDB might not be able to display values
> for
> > such local variables.
> >
> > To solve such problems, either recompile without optimizations, or use a
> > different debug info format, if the compiler supports several such formats.
> For
> > example, GCC, the GNU C/C++ compiler usually supports the `-gstabs' option.
> > `-gstabs' produces debug info in a format that is superior to formats such
> as
> > COFF. You may be able to use DWARF2 (`-gdwarf-2'), which is also an
> effective
> > form for debug info. See section `Options for Debugging Your Program or GNU
> CC'
> > in Using GNU CC, for more information."
> >
> > I wanted to keep the optimization option, so I tried to recompile with GCC,
> > using the -gstabs and -gdwarf-2 options, and even -g3, with this very
> simple
> > program:
> > int main(void){
> > int a = 1;
> > int b = 2;
> > int c = a+b;
> >
> > printf("Value c = %d \n", c);
> > }
> >
> > But still couldn't display the variables a, b and c!
>
> That's because if you ask for the compiler to optimize, it
> will change this program to
>
> int main(void){
> printf ("Value c = %d \n", 3");
> }
>
> if it was a bit cleverer, it might even change it to
>
> int main(void){
> printf ("Value c = 3 \n");
> }
>
> but in either case a,b, and c are gone!
>
> It might be theoretically possible to retain the values of
> a,b,c in the debugging information, but this is a huge amount
> of work, and not something likely to be done in the near future.
>
> > Is there a particular compiling option configuration to set?
>
> Yes, -O0, if you want junk code kept around for debugging
> purposes, you have to ask for it!
> >
> > Is there a particular compiling option configuration to set?
> >
> > Many thanks in advance.
> >
> > Regards.
>
>
next prev parent reply other threads:[~2008-09-02 21:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:27 J R
2008-09-02 21:36 ` Robert Dewar
2008-09-02 21:45 ` jreiver [this message]
2008-09-02 21:50 ` Robert Dewar
2008-09-02 21:57 ` Joel Brobecker
2008-09-03 0:05 ` Michael Snyder
2008-09-03 1:53 ` Robert Dewar
2008-09-03 2:52 ` Daniel Jacobowitz
2008-09-03 14:35 ` Robert Dewar
2008-09-03 3:06 ` Frank Ch. Eigler
2008-09-03 4:37 ` Michael Snyder
2008-09-03 14:36 ` Robert Dewar
2008-09-03 18:34 ` Eli Zaretskii
2008-09-03 21:43 ` Robert Dewar
2008-09-04 8:01 ` Andreas Schwab
2008-09-04 10:53 ` Robert Dewar
2008-09-04 14:05 ` Paul Koning
2008-09-04 14:09 ` Robert Dewar
2008-09-04 14:15 ` Paul Koning
2008-09-04 14:17 ` Robert Dewar
2008-09-04 15:55 ` Eli Zaretskii
2008-09-04 18:13 ` Frank Ch. Eigler
2008-09-04 20:46 ` Ulrich Weigand
2008-09-03 0:04 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1220391632.48bdb2d04bfd7@imp.free.fr \
--to=jreiver@free.fr \
--cc=dewar@adacore.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox