From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: new option --readnever & script gstack?
Date: Tue, 23 Nov 2004 11:46:00 -0000 [thread overview]
Message-ID: <200411222223.iAMMNsTb011794@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41A25D23.9080802@redhat.com> (message from Andrew Cagney on Mon, 22 Nov 2004 16:41:55 -0500)
Date: Mon, 22 Nov 2004 16:41:55 -0500
From: Andrew Cagney <ac131313@redhat.com>
Mark Kettenis wrote:
> It's not really clear what it'd actually do. If it really won't read
> in any symbolic debug info, it'll probably be pretty useless.
> Remember we're relying more and more on DWARF CFI to unwind the stack.
Symbolic debug information, for dwarf2 is stuff found in .debug_info.
CFI and eh-frame are lower level than that.
Well, CFI is normally found in .dwarf_frame, which is at the same
level at .debug_info. There is also CFI in .eh_frame, but in general
only for C++ code (or code compiled with -fexceptions). Only on amd64
CFI in .eh_frame is generated by default.
Mark
next prev parent reply other threads:[~2004-11-22 22:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 20:52 Andrew Cagney
2004-11-22 21:42 ` Mark Kettenis
2004-11-22 22:24 ` Andrew Cagney
2004-11-23 11:46 ` Mark Kettenis [this message]
2004-11-23 12:28 ` Eli Zaretskii
2004-11-23 16:34 ` Andrew Cagney
2004-11-23 21:21 ` Eli Zaretskii
2004-11-23 21:46 ` Andrew Burgess
2004-11-24 9:19 ` Eli Zaretskii
2004-11-29 16:11 ` Andrew Cagney
2004-11-29 16:14 ` Daniel Jacobowitz
2004-11-29 17:50 ` Daniel Jacobowitz
2004-11-29 22:08 ` Eli Zaretskii
2004-11-24 18:04 ` Frank Ch. Eigler
2004-11-23 16:58 Bloch, Jack
2004-11-23 20:45 ` Eli Zaretskii
2004-11-24 3:44 Bloch, Jack
2004-11-24 6:56 ` 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=200411222223.iAMMNsTb011794@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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