From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8a1ec9efc59551c37ee2638fb0d006c1@yourdomain.dom>
From: dbailey27@ameritech.net
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] Do the Pool Voodoo like I do
Date: Thu, 19 Feb 2004 19:52:58 -0500
Topicbox-Message-UUID: ef6cdb3e-eacc-11e9-9e20-41e7f4b1d025

Hey all,
	I'm having a bit of trouble with the malloc
library. I've got an algorithm that dynamically
allocates memory char by char using realloc in
a loop. However, the lib seems to be having some
internal problem. I've got seriously unoptimized
code handling the token stream this algorithm
parses, so there are two cases for the crash below:
	1) my unoptimized code is allocating too much
	    heap and that's causing the panic
	2) there is an internal alloc bug that I'm triggering

Here's the panic info:

mem user overflow
pool sbrkmem block d9a0
hdr 0a110c09 00000020 000023b5 00001f3e 0023ff24 caf0f1fe
tail 0a110c09 00000020 000023b5 00001f3e 0023ff24 caf0f1fe | ef1500be 00000020
user data 00 3e 1f 00  00 24 ff 23 | 00 fe f1 f0  ca be 00 15
panic: pool panic
8.out 703: suicide: sys: trap: fault read addr=0x0 pc=0x000065fb
apple%

Any ideas? More info provided on request.

Don (north_)