From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] i386: Do backtrace fallback too
Date: Sat, 29 Jul 2006 18:35:54 +0200 [thread overview]
Message-ID: <200607291835.54379.ak@suse.de> (raw)
In-Reply-To: <20060729075414.GA16118@redhat.com>
On Saturday 29 July 2006 09:54, Dave Jones wrote:
> On Sat, Jul 29, 2006 at 03:00:06AM +0000, Linux Kernel wrote:
> > commit c97d20a6c51067a38f53680d9609b4cf2867d077
> > tree 59867ac01d1b752ba7e520e33f9f84cade6d024e
> > parent b783fd925cdd56d24d164e5bdcb072f2a67aedf4
> > author Andi Kleen <ak@suse.de> Fri, 28 Jul 2006 14:44:57 +0200
> > committer Linus Torvalds <torvalds@g5.osdl.org> Sat, 29 Jul 2006
> > 09:28:00 -0700
> >
> > [PATCH] i386: Do backtrace fallback too
> >
> > Similar patch to earlier x86-64 patch. When the dwarf2 unwinder fails
> > dump the left over stack with the old unwinder.
> >
> > Also some clarifications in the headers.
> >
> > Signed-off-by: Andi Kleen <ak@suse.de>
> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> >
> > arch/i386/kernel/traps.c | 17 ++++++++++++++---
> > 1 files changed, 14 insertions(+), 3 deletions(-)
>
> Hmm, this breaks the build for me..
Hmm, it definitely builds here. Ah do you have UNWIND_INFO
disabled?
> print_symbol("DWARF2 unwinder stuck at %s\n",
> UNW_PC(info.regs));
>
> be using %p ?
Yes good catch.
-Andi
next prev parent reply other threads:[~2006-07-29 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200607290300.k6T306Fc003168@hera.kernel.org>
2006-07-29 7:54 ` [PATCH] i386: Do backtrace fallback too Dave Jones
2006-07-29 10:28 ` Erik Mouw
2006-07-29 16:35 ` Andi Kleen [this message]
2006-07-29 16:42 ` Dave Jones
2006-07-29 16:52 ` Andi Kleen
2006-07-29 17:03 ` Andi Kleen
2006-07-29 17:13 ` Dave Jones
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=200607291835.54379.ak@suse.de \
--to=ak@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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