public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: mark.kettenis@xs4all.nl, eliz@gnu.org, gdb@sourceware.org
Subject: Re: Specify frame by address
Date: Sun, 30 Oct 2011 13:21:00 -0000	[thread overview]
Message-ID: <201110301007.p9UA7LTK032001@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20111029184808.GA31303@host1.jankratochvil.net> (message from	Jan Kratochvil on Sat, 29 Oct 2011 20:48:08 +0200)

> Date: Sat, 29 Oct 2011 20:48:08 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> On Sat, 29 Oct 2011 20:43:25 +0200, Mark Kettenis wrote:
> > > What is it for stabs?  More generally, suppose I wanted to make the
> > > manual more clear on this matter, what could I tell the user about
> > > how to find out this address?
> > 
> > The debug info format isn't really relevant.  It's the architecture
> > that matters.
> 
> If the debug info provides its own unwinder - such as DWARF does - the
> architecture does not matter as it gets fully handled by dwarf2-frame.c.

I know how the code works; I wrote significant parts of it.  The
architecture does matter, since the convention for what stack address
to use as the CFA depends on the architecture.

> It is true anything besides DWARF - like STABS - just falls back to the
> architecture unwinder.

And that is why the DWARF unwinder and the architecture unwinders
should use the same convention.  So far we've always adjusted the
architecture unwinders to match he DWARF unwinder as that was easiest
and the DWARF CFA turned out to be a meaningful address on those
architectures.  But if that turns out not to be the case for some
future architecture we will have to add a gdbarch method for the DWARF
unwinder to call that fixes things up.

  reply	other threads:[~2011-10-30 10:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 17:47 Eli Zaretskii
2011-10-29 18:03 ` Jan Kratochvil
2011-10-29 18:04   ` Eli Zaretskii
2011-10-29 18:48     ` Mark Kettenis
2011-10-29 20:46       ` Jan Kratochvil
2011-10-30 13:21         ` Mark Kettenis [this message]
2011-11-02  9:14           ` Yao Qi
2011-10-30  6:39       ` Eli Zaretskii
2011-10-29 18:43 ` Andreas Schwab
2011-10-29 20:49   ` Eli Zaretskii
2011-11-01 18:58 ` Tom Tromey
2011-11-01 19:23   ` Eli Zaretskii

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=201110301007.p9UA7LTK032001@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).