From: Robert Dewar <dewar@adacore.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: schwab@suse.de, eliz@gnu.org, fche@redhat.com,
msnyder@vmware.com, brobecker@adacore.com, jreiver@free.fr,
gdb@sourceware.org
Subject: Re: how to examine data with compiler optimization option set?
Date: Thu, 04 Sep 2008 14:09:00 -0000 [thread overview]
Message-ID: <48BFEBCE.8080102@adacore.com> (raw)
In-Reply-To: <18623.60121.742830.903401@gargle.gargle.HOWL>
Paul Koning wrote:
> Is the problem inadequate debug information (i.e., the values are
> there, but there isn't debug data that points to the correct registers
> or stack slots) -- or is the problem that the values you want to see
> are dead by the time you get to them and the registers holding them
> have been reused by then? Or something in between, i.e., the values
> are technically dead, but the registers have NOT yet been reused so
> the debug information can (and should) still show where they are.
Well on entry to a function, (if you breakpoint on entry), the
parameters cannot have been overwritten yet I would think!
>
> paul
next prev parent reply other threads:[~2008-09-04 14:09 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
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 [this message]
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=48BFEBCE.8080102@adacore.com \
--to=dewar@adacore.com \
--cc=Paul_Koning@dell.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jreiver@free.fr \
--cc=msnyder@vmware.com \
--cc=schwab@suse.de \
/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