Date: Tue, 27 Mar 2001 00:21:22 -0600
From: "Kenneth A. Strom" <therelic AT voyager DOT net>
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Hunting Sigsev Errors
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 12
Message-ID: <3ac02f4b$0$14446$272ea4a1@news.execpc.com>
Organization: ExecPC Internet - Milwaukee, WI
NNTP-Posting-Host: 225ed8bc.news.execpc.com
X-Trace: DXC=CQdO_;<NCeGb0EN^dS;UdE2BE>7J AT WeMLbCigiU>8_hH4`>8YbCYbkMYLQ7akVn5OIY?mT25 AT 5nnF3;bgVTJdPbH`Ya>D3S\MhF
X-Complaints-To: abuse AT execpc DOT com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Is there anything that will make this easier?  I have gone over the code
many times,
ignored it for a few days, try fully recompiling after del *.o, and
there is usually a sigsev the first time I run the program after
compiling.  What are the best ways of tracking down this type of error
if it is a memory problem, since it says error in free(), but doesn't
give any other info in gdb?  Any suggestions?

Ken.
therelic AT voyager DOT net