From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ivan Di Prima <ivandiprima@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: reliability of registers contents within each frame
Date: Fri, 13 Apr 2012 13:21:00 -0000 [thread overview]
Message-ID: <20120413132127.GD22952@host2.jankratochvil.net> (raw)
In-Reply-To: <4F8723C8.5060900@gmail.com>
On Thu, 12 Apr 2012 20:49:44 +0200, Ivan Di Prima wrote:
> Basically if move "up" and "down" between frames and then display the
> register contents with "info reg" do I see ALL the register captured in that
> frame or just the registers which are "push" on the stack within the source
> code?
"ALL". Which registers are saved by which frame you see in "info frame".
> Also, will optimization affect register values such that even if they are
> not marked "<value optimized out>" by gdb their values will still be
> readable but unreliable?
I was told it applies to gcc-4.0+. While the mail below is not a direct
countercase I trust more just gcc-4.5+:
[patch] Fix regression by me for gcc-4.0...gcc-4.4 i386 -O2 -g parameters (PR 13777)
http://sourceware.org/ml/gdb-patches/2012-02/msg00673.html
Regards,
Jan
prev parent reply other threads:[~2012-04-13 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 18:50 Ivan Di Prima
2012-04-13 13:21 ` Jan Kratochvil [this message]
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=20120413132127.GD22952@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=ivandiprima@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).