From:	"Antonijs Kipans" <anthony AT lbi DOT lnb DOT lv>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Heap structure
Date:	Fri, 28 Sep 2001 18:34:05 +0300
Organization:	Latnet Internet News Site
Lines:	27
Message-ID:	<9p25as$rra$1@milzis.latnet.lv>
References:	<3BA1292B DOT C593DFD8 AT cyberoptics DOT com>
NNTP-Posting-Host:	159.148.113.161
X-Trace:	milzis.latnet.lv 1001691292 28522 159.148.113.161 (28 Sep 2001 15:34:52 GMT)
X-Complaints-To:	usenet AT news DOT latnet DOT lv
NNTP-Posting-Date:	28 Sep 2001 15:34:52 GMT
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

As I stumbled over this myself, there is one unexpected possibility -
you trie to fprintf() into UNOPEN file!

BR,
Anthony

"Eric Rudd" <rudd AT cyberoptics DOT com> wrote in message
news:3BA1292B DOT C593DFD8 AT cyberoptics 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 -