🚀 go-pugleaf

Here's another thing that could break a 68020 machine that I just
realized.  If you *ever* do something like:

char *copystr(s) char *s ; { return(strcpy(mymalloc(strlen(s)),s)) ; }

(not as though I'm advocating that style of programming) but where
mymalloc grabs a chunk of memory, from a previously allocated chunk
or from the system, (and presumably checks for NULL), this could
well work on a 68000 system for a long time.  You'll overwrite the
next byte with a 0, but if that next byte is a pointer, you'll never
notice on a '000, but an '020 will break.

I've been bitten with malloc(strlen), so be careful!  Sometimes it's
a lot more subtle, if you add constants or something because you did
a strcat() and are off by one or something . . .

-tom

-- 
    /-- Tomas Rokicki         ///  Box 2081  Stanford, CA  94309
   / o  Radical Eye Software ///  (TAMU EE '85)   (415) 326-5312
\ /  |  . . . or I       \\\///Join CCFFAALW---Concerned Citzens
 V   |  won't get dressed \XX/Fighting For An Acronym-Less World