linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Tameen Khan" <tameen@cisco.com>
To: "'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>
Cc: "'linuxppc-dev list'" <linuxppc-dev@lists.linuxppc.org>
Subject: RE: stack frame for interrupts/exceptions in PPC
Date: Wed, 28 Apr 2004 10:41:32 -0700	[thread overview]
Message-ID: <008d01c42d48$0baae1a0$273147ab@amer.cisco.com> (raw)
In-Reply-To: <1083118036.20092.30.camel@gaston>


> > > I am tryting to implement kernel backtracing for PPC.
>
> What do you mean ? There is already working backtrace code in
> the kernel, both in the Oops code and in xmon.

Did not know that. Am new to linux and ppc.
I'm porting lkcdutils for PPC. It picks up a kernal core dump and among
other things has to generate backtraces from it.

Thanks for the info
Tameen


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-04-28 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28  1:11 stack frame for interrupts/exceptions in PPC Tameen Khan
2004-04-28  2:07 ` Benjamin Herrenschmidt
2004-04-28 17:41   ` Tameen Khan [this message]
2004-04-29 16:31     ` linas

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='008d01c42d48$0baae1a0$273147ab@amer.cisco.com' \
    --to=tameen@cisco.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).