From: Harvey Harrison <harvey.harrison@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Make the 32 bit Frame Pointer backtracer fall back to traditional
Date: Wed, 09 Jan 2008 22:21:45 -0800 [thread overview]
Message-ID: <1199946105.19760.5.camel@brick> (raw)
In-Reply-To: <20080109220508.686bbda4@laptopd505.fenrus.org>
On Wed, 2008-01-09 at 22:05 -0800, Arjan van de Ven wrote:
> Subject: Make the 32 bit Frame Pointer backtracer fall back to traditional
> From: Arjan van de Ven <arjan@linux.intel.com>
>
> The 32 bit Frame Pointer backtracer code checks if the EBP is valid
> to do a backtrace; however currently on a failure it just gives up
> and prints nothing. That's not very nice; we can do better and still
> print a decent backtrace.
>
> This patch changes the backtracer to fall back to the non-framepointer
> backtracer if the EBP value isn't within the expected range; so on weird
> stack corruption cases we get at least something out...
>
Arjan, I've been doing some work on traps_32.c porting over the
oops_begin()/oops_end()/_die() arrangement from traps_64.c and
then use it in unifying some more parts of fault.c.
If you have other work in this area, I'll hold off until your stuff
goes in...feel free to send me any work in progress stuff and I can
try to coordinate with you.
Harvey
next prev parent reply other threads:[~2008-01-10 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 6:05 Make the 32 bit Frame Pointer backtracer fall back to traditional Arjan van de Ven
2008-01-10 6:21 ` Harvey Harrison [this message]
2008-01-10 12:46 ` Ingo Molnar
2008-01-10 15:15 ` Arjan van de Ven
2008-01-10 6:55 ` Ingo Molnar
2008-01-10 16:36 ` Linus Torvalds
2008-01-10 16:49 ` Arjan van de Ven
2008-01-11 4:35 ` Arjan van de Ven
2008-01-11 11:54 ` Olaf Dietsche
2008-01-11 19:41 ` Linus Torvalds
2008-01-11 19:56 ` Arjan van de Ven
2008-01-11 22:01 ` Theodore Tso
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=1199946105.19760.5.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.