mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: roland@topspin.com, agl@us.ibm.com, mlxk@mellanox.co.il,
	linux-kernel@vger.kernel.org
Subject: Re: stack dumps, CONFIG_FRAME_POINTER and i386 (was Re: sysrq shows impossible call stack)
Date: Tue, 20 Apr 2004 18:41:09 -0700	[thread overview]
Message-ID: <20040420184109.6876b3d9.akpm@osdl.org> (raw)
In-Reply-To: <20040420183915.4eee560c.akpm@osdl.org>

Andrew Morton <akpm@osdl.org> wrote:
>
> Roland Dreier <roland@topspin.com> wrote:
>  >
>  >     Adam> This problem was annoying me a few months ago so I coded up
>  >     Adam> a stack trace patch that actually uses the frame pointer.
>  >     Adam> It is currently maintained in -mjb but I have pasted below.
>  >     Adam> Hope this helps.
>  > 
>  > Thanks, that looks really useful.  What is the chance of this moving
>  > from -mjb to mainline?
> 
>  Good, but it needs to be updated to do the right thing with 4k stacks when
>  called from interrupt context.

Also, I'd like to be convinced that it does the right thing across assembly
code which doesn't set up a correct frame pointer, such as down().

I assume it will simply skip that frame altogether?

  reply	other threads:[~2004-04-21  1:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 15:45 sysrq shows impossible call stack Eli Cohen
2004-04-20 16:26 ` Roland Dreier
2004-04-20 17:36   ` Eli Cohen
2004-04-20 17:51     ` stack dumps, CONFIG_FRAME_POINTER and i386 (was Re: sysrq shows impossible call stack) Roland Dreier
2004-04-20 20:26       ` Adam Litke
2004-04-21  0:12         ` Roland Dreier
2004-04-21  1:39           ` Andrew Morton
2004-04-21  1:41             ` Andrew Morton [this message]
2004-04-21 23:28               ` Adam Litke
2004-04-21 23:50                 ` Andrew Morton
2004-04-22 18:25                   ` Adam Litke

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=20040420184109.6876b3d9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=agl@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlxk@mellanox.co.il \
    --cc=roland@topspin.com \
    /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
all inboxes | Powered by JetHome®