From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: mark.kettenis@xs4all.nl, nickrob@snap.net.nz, gdb@sources.redhat.com
Subject: Re: info frame
Date: Mon, 17 Apr 2006 12:16:00 -0000 [thread overview]
Message-ID: <200604171053.k3HArwYH004481@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <u1wvwzdyt.fsf@gnu.org> (message from Eli Zaretskii on Mon, 17 Apr 2006 13:35:54 +0300)
> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
> elgar.sibelius.xs4all.nl
> X-Spam-Level:
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed
> version=3.1.0
> Date: Mon, 17 Apr 2006 13:35:54 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: nickrob@snap.net.nz, gdb@sources.redhat.com
> Reply-to: Eli Zaretskii <eliz@gnu.org>
> X-IsSubscribed: yes
> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
> Sender: gdb-owner@sourceware.org
> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> X-UTwente-MailScanner: Found to be clean
> X-MailScanner-From: gdb-return-24948-m.m.kettenis=alumnus.utwente.nl@sourceware.org
> X-XS4ALL-DNSBL-Checked: mxdrop40.xs4all.nl checked 192.87.17.19 against DNS blacklists
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0 ()
> X-XS4ALL-Spam: NO
> Envelope-To: mark.kettenis@xs4all.nl
> X-UIDL: 1145270175._smtp.mxdrop40.36794,S=3326
>
> > Date: Mon, 17 Apr 2006 10:58:43 +0200 (CEST)
> > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > CC: nickrob@snap.net.nz, gdb@sources.redhat.com
> >
> > > > Yes, current GDB uses the convention that the frame address is the
> > > > Canonical Frame Address (CFA) as used by the DWARF 2 Call Frame Info
> > > > (CFI).
> > >
> > > Does this mean that, if the debug info is stabs or something other
> > > than DWARF 2, a different frame address will be displayed for the same
> > > code?
> >
> > No. All the different unwinders use the same convention.
>
> Don't you glean the information from the debug info? At least for
> functions that violate the normal call frame, you probably must, no?
The only debug format that contains the information is DWARF 2/3. The
other unwinders all code scanning techniques to find out the CFA.
Those have been adapted to match the CFA as used by GCC.
prev parent reply other threads:[~2006-04-17 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 0:37 Nick Roberts
2006-04-17 1:33 ` Mark Kettenis
2006-04-17 5:54 ` Nick Roberts
2006-04-17 5:57 ` Daniel Jacobowitz
2006-04-17 6:37 ` Nick Roberts
2006-04-17 7:38 ` Eli Zaretskii
2006-04-17 8:41 ` Vladimir Prus
2006-04-17 14:01 ` Daniel Jacobowitz
2006-04-18 8:40 ` Eli Zaretskii
2006-04-17 7:35 ` Eli Zaretskii
2006-04-17 9:05 ` Mark Kettenis
2006-04-17 11:21 ` Eli Zaretskii
2006-04-17 12:16 ` Mark Kettenis [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=200604171053.k3HArwYH004481@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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