From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Adam Litke <agl@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [RFC] Smarter stack traces using the frame pointer
Date: Wed, 05 Nov 2003 11:56:34 -0800 [thread overview]
Message-ID: <119200000.1068062194@flay> (raw)
In-Reply-To: <20031105132138.59326dd4.sfr@canb.auug.org.au>
>> I was working on this for the mjb tree but I thought I'd throw it out
>> here in case anyone else finds it interesting. This simple change to
>> the stack trace code uses the frame pointer to do the trace instead of
>> assuming any kernel address on the stack is a return address. It makes
>> for much more readable stack traces.
>
> I was asked by a colleague to do the same thing and came up with this
> alternative version which, I think, gets it mostly right - I am not
> sure about the stack trace from an OOPS.
>
> Don't bother to tell me this is a bit of a hack - I know :-)
>
> Patch relative to 2.6.0-test9.
What's the difference between the two patches, apart from the size?
Better error handling / functionality somehow?
M.
next prev parent reply other threads:[~2003-11-05 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 22:13 [RFC] Smarter stack traces using the frame pointer Adam Litke
2003-11-05 2:21 ` Stephen Rothwell
2003-11-05 19:56 ` Martin J. Bligh [this message]
2003-11-06 11:51 ` Stephen Rothwell
2003-11-06 15:21 ` Martin J. Bligh
2003-11-10 17:46 ` Adam Litke
2003-11-06 20:08 Dan Kegel
[not found] <OhH5.6Y2.13@gated-at.bofh.it>
[not found] ` <QouH.36G.7@gated-at.bofh.it>
2003-11-10 18:06 ` Andi Kleen
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=119200000.1068062194@flay \
--to=mbligh@aracnet.com \
--cc=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).