Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!munnari.oz.au!bruce!trlluna!titan!rhea!aduncan
From: aduncan@rhea.trl.OZ.AU (Allan Duncan)
Newsgroups: comp.sys.amiga.programmer
Subject: AllocMem fun and games on a 3000
Message-ID: <1991May31.044825.10677@trl.oz.au>
Date: 31 May 91 04:48:25 GMT
Article-I.D.: trl.1991May31.044825.10677
Sender: news@trl.oz.au (USENET News System)
Organization: Telecom Research Labs, Melbourne, Australia
Lines: 17

This is for an acquaintance who hasn't go net access,.

His problem was with AllocMem returning bad pointers.  This was in code
that had been running w/o problems on 2000's.

Turns out that he was over-running a string allocation by one byte.
This would (if the allocation was a multiple of 8) clobber the first byte
of the memseg pointer that followed it.  On 24 bit address space, this
was alright, since the overwrite was a null byte, but for 32 bit fast
addresses on the 3000, fireworks mode!

So, be warned.

Allan Duncan	ACSnet	 a.duncan@trl.oz
(+613) 541 6708	Internet a.duncan@trl.oz.au
		UUCP	 {uunet,hplabs,ukc}!munnari!trl.oz.au!a.duncan
Telecom Research Labs, PO Box 249, Clayton, Victoria, 3168, Australia.