Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ucsd!ucsdhub!hp-sdd!hplabs!hpda!hpcupt1!hpisod1!renglish
From: renglish@hpisod1.HP.COM (Robert English)
Newsgroups: comp.lang.c
Subject: Re: Re: Contiguous address spaces
Message-ID: <10130001@hpisod1.HP.COM>
Date: 14 Oct 88 20:31:15 GMT
References: <1988Oct13.210524.22909@ateng.ateng.com>
Organization: Hewlett Packard, Cupertino
Lines: 12

/ chip@ateng.ateng.com (Chip Salzenberg) /  6:05 pm  Oct 13, 1988 /

> Can you say "catch SIGSEGV, call sbrk() and retry"?  I knew you could.

The sh behavior which is (or was at one time) appalling was its
implicit assumption that memory was contiguous and grew in a particular
direction.  This allowed it to write increasing strings off the end of
its static memory space and use the signal catching code you described
to notice when it ran out.  It was an elegant solution in its way, but
it imbedded assumptions about the machine architecture in the code.

--bob--