mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: arjan@fenrus.demon.nl
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic show_stack facility
Date: Fri, 29 Mar 2002 10:25:36 -0800	[thread overview]
Message-ID: <15524.45472.231096.377756@napali.hpl.hp.com> (raw)
In-Reply-To: <200203291716.g2THGNq08251@fenrus.demon.nl>

>>>>> On Fri, 29 Mar 2002 17:16:23 GMT, arjan@fenrus.demon.nl said:

  >> BTW: this is not at all an ia64-specific issue.  It applies to
  >> any arch that doesn't maintain a frame pointer on the stack.
  >> Basic compiler technology.

  Arjan> oh you mean like x86 ?

As far as I know, the x86 version of show_trace() still relies on the
fact that (a) return addresses are stored on the memory stack, (b)
they are stored in the order in which the routines were called, and
(c) that there aren't too many other values on the stack that look
like kernel text addresses.  As long as an x86 compiler uses the CALL
instruction, that should be the case.  But this certainly isn't the
case for all architectures (though I do agree that it is a heuristic
should work reasonably well for several architectures).

	--david

  reply	other threads:[~2002-03-29 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29 15:23 Christoph Hellwig
2002-03-29 15:46 ` David Mosberger
2002-03-29 16:06   ` Christoph Hellwig
2002-03-29 17:08     ` David Mosberger
2002-03-29 17:16       ` arjan
2002-03-29 18:25         ` David Mosberger [this message]
2002-03-30 10:06           ` Kai Henningsen
2002-03-29 17:36       ` Andrew Morton
2002-03-29 18:26         ` David Mosberger
2002-03-29 18:34         ` Christoph Hellwig
2002-03-29 18:41           ` Andrew Morton
2002-03-30  3:05 Keith Owens
2002-03-30  3:31 ` Andrew Morton

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=15524.45472.231096.377756@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=arjan@fenrus.demon.nl \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®