From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] too good to pass up (SRB Comments)
Date: Mon, 1 May 2006 23:32:09 -0700 [thread overview]
Message-ID: <1146551530.30018.11.camel@123> (raw)
In-Reply-To: <790d46fb49d0b5be9d9300797ec1e698@coraid.com>
On Fri, 2006-04-28 at 09:10 -0400, Brantley Coile wrote:
> That was really John Mashy's fault, as I understand it. He suggested
> it to SRB. I had to deal with it when I ported V7 to the 68K. Too
> bad every processor wasn't as clean in this reguard as the PDP-11.
>
> For those who might not have heard of this, SRB caught segfault
> signals, allocated more memory and just returned. The instruction
> that caused the segfault would restart. It was an automatic memory
> allocator. Problem was that not all processors could pull off this
> sort of stunt.
That's some tricky programming! Do you know of any place one can get
an access to the original code ?
Thanks,
Roman.
next prev parent reply other threads:[~2006-05-02 6:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:01 [9fans] too good to pass up erik quanstrom
2006-04-28 13:10 ` [9fans] too good to pass up (SRB Comments) Brantley Coile
2006-04-28 14:16 ` OT: " Dave Lukes
2006-04-28 14:18 ` Brantley Coile
2006-05-02 6:32 ` Roman Shaposhnik [this message]
2006-05-01 21:22 ` Taj Khattra
2006-04-28 21:57 ` [9fans] too good to pass up Charles Forsyth
2006-04-28 13:30 [9fans] too good to pass up (SRB Comments) erik quanstrom
2006-04-28 21:13 ` geoff
2006-04-28 21:06 ` quanstro
2006-04-30 10:35 ` Richard Miller
2006-05-01 1:01 ` geoff
2006-05-01 9:21 ` Richard Miller
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=1146551530.30018.11.camel@123 \
--to=rvs@sun.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).