From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] too good to pass up (SRB Comments)
Date: Fri, 28 Apr 2006 08:30:11 -0500 [thread overview]
Message-ID: <2a79a565395945cd1a40d7c74d6a53b9@quanstro.net> (raw)
it was not cleaned up in the xinu bsd source. iirc, on a vax,
it would coredump fairly reliably. i spent some time trying
to figure out what the malfunction was, but never could.
i blamed nfs, since it was the convient thing to do, and
started using byron's rc.
the coding style was never a significant problem. if it were,
i could have easily written a script to replace the odd #defines.
- erik
On Fri Apr 28 08:12:19 CDT 2006, brantley@coraid.com 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.
>
> Geoff cleaned this up years ago.
>
> > not even his allocator?
> >
> > - erik
> >
> > On Fri Apr 28 08:02:29 CDT 2006, brantley@coraid.com wrote:
> >> > Not that I'm defending writing C as
> >> > though it were Algol 68...
> >>
> >> I kind of liked it after the initial shock.
> >> Even inspired the Obfuscated C Contest.
> >> I don't think SRB's code was obfuscated, though.
> >>
> >>
>
>
next reply other threads:[~2006-04-28 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:30 erik quanstrom [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-05-02 6:32 ` Roman Shaposhnik
2006-05-01 21:22 ` Taj Khattra
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=2a79a565395945cd1a40d7c74d6a53b9@quanstro.net \
--to=quanstro@quanstro.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).