From: "Gorka guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] pointer to the last TOS
Date: Thu, 2 Mar 2006 15:57:59 +0100 [thread overview]
Message-ID: <599f06db0603020657u19643c27nad00cbf2998bf877@mail.gmail.com> (raw)
I have been doing some experiments and reading some code and I have arrived
to the (possibly wrong) conclusion that in the stack there is no pointer to the
TOS before a function was called (I am using 8c)
If this is true, how is the state of the stack
recovered after return?. Can anyone point me to a place where I can read
some documentation or something to solve this kind of doubt.
I read some acid and 8c code, but was too complicated for such a simple doubt.
(I will study 8c but not any time soon). I tried printing the stack of
a process and
didnt find it there. I also read asm.ps and comp.ps.
--
- curiosity sKilled the cat
next reply other threads:[~2006-03-02 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 14:57 Gorka guardiola [this message]
2006-03-02 15:23 ` Brantley Coile
2006-03-02 15:34 ` Gorka guardiola
2006-03-03 1:54 ` geoff
2006-03-02 15:24 ` 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=599f06db0603020657u19643c27nad00cbf2998bf877@mail.gmail.com \
--to=paurea@gmail.com \
--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).