From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: systemtap@sourceware.org, roland@redhat.com
Subject: [Query] Re: dwarf unwinder (only works on i386/x86_64)
Date: Tue, 28 Apr 2009 18:02:00 -0000 [thread overview]
Message-ID: <49F74546.8040206@linux.vnet.ibm.com> (raw)
In-Reply-To: <1239977157.2336.33.camel@fedora.wildebeest.org>
Hi Mark,
An elementary query regarding the dwarf-unwinder implementation...
Mark Wielaard wrote:
> ......
>
> I am working on using the dwarf unwinder also for user space
> backtracing. First using the debug_frame tables that we also are using
> for the kernel case, but maybe switching to the eh_frame tables (it
> isn't clear which one is really the most accurate at the moment, we
> might need to consult both, but I am trying to avoid doing that for
> now).
>
>
I was trying to contrast the ".eh_frame" vs ".debug_frame"
specifications for keeping track of stack backtraces. Both appear rather
similar wrt information they maintain.
The Exception header ".eh_frame" section seems to be present in vmlinux
even when kernel is compiled without debuginfo.
i. what gcc flags cause this section to be compiled ?
ii. This section seemingly appears to be a better bet than DWARF to base
the unwinder on--- because a ".debug_frame" based unwinder might not be
useful in case of a kernel complied without debuginfo.
Looks like I'm missing some reasoning here, could you throw some light ?
:-)
> Cheers,
>
> Mark
>
>
Regards,
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2009-04-28 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 14:06 Mark Wielaard
2009-04-21 20:58 ` dwarf unwinder (only works on i386/x86_64) - now with user space unwinding Mark Wielaard
2009-05-21 8:03 ` dwarf unwinder (only works on i386/x86_64) - now with eh_frame and debug_frame fallback Mark Wielaard
2009-05-21 18:44 ` Roland McGrath
2009-05-21 22:57 ` Mark Wielaard
2009-05-22 1:19 ` Roland McGrath
2009-04-28 18:02 ` Prerna Saxena [this message]
2009-04-28 18:19 ` [Query] Re: dwarf unwinder (only works on i386/x86_64) Roland McGrath
2009-04-28 19:52 ` Mark Wielaard
2009-04-28 20:15 ` Roland McGrath
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=49F74546.8040206@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.com \
--cc=mjw@redhat.com \
--cc=roland@redhat.com \
--cc=systemtap@sourceware.org \
/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).