Date: Tue, 27 Mar 2001 09:01:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Kenneth A. Strom" <therelic AT voyager DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Hunting Sigsev Errors
In-Reply-To: <3ac02f4b$0$14446$272ea4a1@news.execpc.com>
Message-ID: <Pine.SUN.3.91.1010327085817.19916G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 27 Mar 2001, Kenneth A. Strom wrote:

> 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?

Did you see and try the advice in section 12.2 of the DJGPP FAQ list?

If you already tried that and it didn't help, please post the details: 
sample crash messages with traceback after running SYMIFY, the code 
fragment that crashes (based on what SYMIFY says), etc.

Also, what do you mean by ``doesn't give any other info in gdb''?  Does 
the program crash when run under GDB?  If so, you should be able to 
examine the variables which are involved in the crash and see which one 
is corrupted, at the very least.