Message-ID:	<3BA1292B.C593DFD8@cyberoptics.com>
From:	Eric Rudd <rudd AT cyberoptics DOT com>
Organization:	CyberOptics
X-Mailer:	Mozilla 4.72 [en] (Win95; U)
X-Accept-Language:	en,pdf
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Heap structure
Lines:	17
Date:	Thu, 13 Sep 2001 16:46:19 -0500
NNTP-Posting-Host:	38.196.93.9
X-Trace:	client 1000417591 38.196.93.9 (Thu, 13 Sep 2001 17:46:31 EDT)
NNTP-Posting-Date:	Thu, 13 Sep 2001 17:46:31 EDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I have a DJGPP program that is bombing with a SIGSEGV error.  I have
reason to believe that the program has an array overflow that is
corrupting the structure of the heap.  (The program actually bombs in a
malloc call inside fprintf, but at this point I have no convincing
reason to believe that a system function bug is to blame.)

I would like to write a subroutine that walks the heap and checks its
integrity, so that I can isolate the bug.  Another correspondent to
c.o.m.d. was interested in writing a heap-checker some time ago, but I
haven't heard any more about it.

Does anyone know where the heap structure is documented, or is the
malloc.c source the only documentation?

-Eric Rudd
rudd AT cyberoptics DOT com

- Raw text -