From: Robert Dewar <dewar@adacore.com>
To: jreiver@free.fr
Cc: gdb@sourceware.org
Subject: Re: how to examine data with compiler optimization option set?
Date: Tue, 02 Sep 2008 21:50:00 -0000 [thread overview]
Message-ID: <48BDB4E2.9010301@adacore.com> (raw)
In-Reply-To: <1220391632.48bdb2d04bfd7@imp.free.fr>
jreiver@free.fr wrote:
> 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.
It does not say that, it says that "depending on the support for such
cases offered by the debug format" ... it does not imply or state that
any debug format will be able to preserve the information (in the
general case it is enormously difficult to preserve this information).
>
> Isn't that possible at all? (I am currently evaluating the debugging facilities
> of gdb)
>
No it is not possible.
next prev parent reply other threads:[~2008-09-02 21:50 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
2008-09-02 21:50 ` Robert Dewar [this message]
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=48BDB4E2.9010301@adacore.com \
--to=dewar@adacore.com \
--cc=gdb@sourceware.org \
--cc=jreiver@free.fr \
/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