From:	jazir <entropic AT mpx DOT com DOT au>
Newsgroups:	comp.os.msdos.djgpp
Subject:	{more} upgrade chaos
Date:	Wed, 12 Jan 2000 13:19:57 +1100
Organization:	Optus Internet
Lines:	24
Message-ID:	<387BE4CD.1070AA75@mpx.com.au>
NNTP-Posting-Host:	wdcax5-113.dialup.optusnet.com.au
Mime-Version:	1.0
X-Trace:	news1.mpx.com.au 947646933 18531 198.142.59.113 (12 Jan 2000 03:15:33 GMT)
X-Complaints-To:	abuse AT mpx DOT com DOT au
NNTP-Posting-Date:	12 Jan 2000 03:15:33 GMT
X-Mailer:	Mozilla 4.5 [en] (Win95; I)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

hey all,

  thanks fr posting that Mark, i'm glad i'm not the only one with
troubles.

more trouble:

  today i recompiled the program and tried again...rather then in free(), 
the SIGSEGV occurs in malloc().  i am fairly certain that these kinds of
errors should *never* happen.  there is nothing my code can do that should
make free() fail is there?

  even if i was freeing NULL pointers, {which i'm not}, the LibC documentation
says this would not crash.  after deleting my old installation, i'm now w/out
a working C compiler.....helllllp me!  hehe

  another problem:   i was compiling yet another of my old programs, and i
got the SIGSEGV from free(), but the stack displayed after the crash only
had free in it..not where it was called from.  this is all very weird.


catch-ya's later,
jazir.

- Raw text -