9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rdbfs
Date: Wed, 24 Aug 2005 18:33:58 -1000	[thread overview]
Message-ID: <Pine.BSI.4.61.0508241829220.26990@malasada.lava.net> (raw)
In-Reply-To: <5ee344bb91dbfd0f818b683a68a31583@coraid.com>

> acid: lstk()
> <stdin>:2: (error) no stack frame

I used rdbfs often when working with sparc, but over tcp (minor
mods to rdbfs to not set baud, and then a small shim to invoke
it on an fd from dial()) since the computer was connected to
the serial port of a non-plan9 computer.

As for the stack frame -- I found it useful to modify the
acid startup files (/sys/lib/acid/*) to allow you to pick
which set of registers to use.  This lets you set the registers
to some ureg location such as the ureg's at the time of
an exception/trap so that you can trace back from that point.
The changes are fairly straightforward -- read registers from
offsets starting at the specified address rather than from
offset zero.  The big change is altering all accesses to registers
to go through the ureg pointer (which would default to zero for
real registers).

You can also try to manually interpret the stack frame, but its
a bit tedious without frame pointers.

Tim Newsham
http://www.lava.net/~newsham/


  reply	other threads:[~2005-08-25  4:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 20:33 Brantley Coile
2005-08-24 20:53 ` Russ Cox
2005-08-24 22:50   ` Sape Mullender
2005-08-24 22:56     ` Brantley Coile
2005-08-24 23:19       ` Russ Cox
2005-08-24 23:23         ` Brantley Coile
2005-08-25  4:33           ` Tim Newsham [this message]
2005-08-24 23:06     ` Steve Simon
2005-08-25  2:41   ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2005-08-24 17:00 Brantley Coile
2005-08-24 17:13 ` Russ Cox
2005-08-24 17:25   ` Brantley Coile
2005-08-24 17:39     ` Russ Cox

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=Pine.BSI.4.61.0508241829220.26990@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    /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).