From: Daniel Jacobowitz <drow@false.org>
To: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
David Daney <ddaney@caviumnetworks.com>,
gdb@sourceware.org
Subject: Re: GDB interactions with GCC
Date: Tue, 03 Nov 2009 18:01:00 -0000 [thread overview]
Message-ID: <20091103180127.GA7855@caradoc.them.org> (raw)
In-Reply-To: <c568a2600911030954w41581a25u6483ec65cfb6bac9@mail.gmail.com>
On Tue, Nov 03, 2009 at 12:54:54PM -0500, Jean Christophe Beyler wrote:
> On my architecture, I can have the code for foo reduced to :
>
> add FirstInputRegister, FirstInputRegister, 1
> call bar
> branch return.
>
> Therefore, once I'm in bar, the input register that foo had has been
> lost since it's been incremented. The original value of a has been
> lost since it is not in a particular register, was not spilled.
>
> In this case, how does GDB handle it ?
GDB will report that the value is not available. If you compile
without optimization, GCC will generally save it in a stack slot, and
the value will be available.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-11-03 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 22:44 Jean Christophe Beyler
2009-11-02 23:16 ` David Daney
2009-11-03 17:22 ` Jean Christophe Beyler
2009-11-03 17:38 ` Paul Pluzhnikov
2009-11-03 17:55 ` Jean Christophe Beyler
2009-11-03 18:01 ` Daniel Jacobowitz [this message]
2009-11-03 18:09 ` Jean Christophe Beyler
2009-11-03 18:14 ` Daniel Jacobowitz
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=20091103180127.GA7855@caradoc.them.org \
--to=drow@false.org \
--cc=ddaney@caviumnetworks.com \
--cc=gdb@sourceware.org \
--cc=jean.christophe.beyler@gmail.com \
--cc=ppluzhnikov@google.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