From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: Hunting Sigsev Errors Date: Tue, 27 Mar 2001 01:29:03 -0500 Organization: Global Crossing Telecommunications Lines: 24 Sender: UNKNOWN AT 209-130-186-49 DOT nas7 DOT roc DOT gblx DOT net Message-ID: <99pbt6$146i$1@node17.cwnet.frontiernet.net> References: <3ac02f4b$0$14446$272ea4a1 AT news DOT execpc DOT com> NNTP-Posting-Host: 209-130-186-49.nas7.roc.gblx.net X-Trace: node17.cwnet.frontiernet.net 985674470 37074 209.130.186.49 (27 Mar 2001 06:27:50 GMT) X-Complaints-To: abuse AT frontiernet DOT net NNTP-Posting-Date: 27 Mar 2001 06:27:50 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 "Kenneth A. Strom" wrote in message news:3ac02f4b$0$14446$272ea4a1 AT news DOT execpc 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? > if in free(), make sure the pointer is valid. Good Luck -- Alexei A. Frounze alexfru [AT] chat [DOT] ru http://alexfru.chat.ru http://members.xoom.com/alexfru/ http://welcome.to/pmode/