Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Peter Popov <ppopov@redcreek.com>
To: "linux@engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: general mips question
Date: Mon, 15 May 2000 14:09:17 -0700	[thread overview]
Message-ID: <3920677D.221EC442@redcreek.com> (raw)


Is it possible to "walk" the stack on a mips system after a crash to
figure out all the functions which were called upto and including the
function where the crash occurred?  For example, I can do that on an
i960 system because of the help I get from the cpu in creating a stack
and saving some registers for every function call.  If A called B which
called C which called D, I can walk the stack on an i960 system and
figure out how I got to D. But I can't quite figure out how to do that
in software on a mips system.  All I can get is the return address of
the current function -- eg if the system crashed in D, all I can get is
the return address which is somewhere in function C.  Any ideas?

Thanks,

Pete

             reply	other threads:[~2000-05-15 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-15 21:09 Peter Popov [this message]
2000-05-15 21:32 ` general mips question Ralf Baechle

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=3920677D.221EC442@redcreek.com \
    --to=ppopov@redcreek.com \
    --cc=linux@cthulhu.engr.sgi.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