From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: PR gdb/856
Date: Mon, 29 Sep 2008 18:03:00 -0000 [thread overview]
Message-ID: <20080929180225.GA25971@caradoc.them.org> (raw)
In-Reply-To: <20080929171750.GB3811@adacore.com>
On Mon, Sep 29, 2008 at 10:17:50AM -0700, Joel Brobecker wrote:
> > Daniel's answer is here, but I never got back to it:
> > http://sourceware.org/ml/gdb-patches/2008-06/msg00036.html
>
> PC and block: I don't see why passing the block would be required
> for inlining support - as I understand it, we can always compute
> the actual block from the PC. No?
No. There can be more than one block at the PC.
Normally this isn't a big deal. Anything from blocks further out is
visible further in. There are two exceptions. One of them is already
a problem and GDB does not support it helpfully: shadowed variables.
{
int x;
{
int x;
...
}
}
The other is more noticeable; inlining. When you say "up" you move to
the call site. And the call site might be in a different file, and
have different macros defined.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-29 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 16:58 Tom Tromey
2008-09-29 16:57 ` Joel Brobecker
2008-09-29 17:12 ` Pedro Alves
2008-09-29 17:18 ` Joel Brobecker
2008-09-29 18:03 ` Daniel Jacobowitz [this message]
2008-09-30 0:13 ` Joel Brobecker
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=20080929180225.GA25971@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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