public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: Prerna Saxena <prerna@linux.vnet.ibm.com>, systemtap@sourceware.org
Subject: Re: [Query] Re: dwarf unwinder (only works on i386/x86_64)
Date: Tue, 28 Apr 2009 20:15:00 -0000	[thread overview]
Message-ID: <20090428201506.4B972FC3BF@magilla.sf.frob.com> (raw)
In-Reply-To: Mark Wielaard's message of  Tuesday, 28 April 2009 21:51:23 +0200 <1240948283.3822.13.camel@hermans.wildebeest.org>

> The original choice for using debug_frame was because it was always
> available (since we required debuginfo already) and it was complete. GCC
> 4.4 changed this though (and the uprobes_ustack.exp test does indeed
> fail when build with gcc 4.4). [...]

To be fair, 4.4 only changed one of the many wrinkles that fold together
here.  It was never really the case that either one was always complete
when present.  (It's a big hairy subject.)

      reply	other threads:[~2009-04-28 20:15 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 ` [Query] Re: dwarf unwinder (only works on i386/x86_64) Prerna Saxena
2009-04-28 18:19   ` Roland McGrath
2009-04-28 19:52     ` Mark Wielaard
2009-04-28 20:15       ` Roland McGrath [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=20090428201506.4B972FC3BF@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=mjw@redhat.com \
    --cc=prerna@linux.vnet.ibm.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).