Date:	Wed, 6 Dec 1995 08:13:31 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Nicholas Marrone <nmarrone AT smartdocs DOT com>
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Sigsev

On Sat, 2 Dec 1995, Nicholas Marrone wrote:

> with other programs, and have had no troubles, but now when I try and
> run the executable I get an error about a signal at Segsev. Could
> someone please explain to me what this means, and if possible, how to
> fix it? At first I thought this error was due to CWSDPMI, but then I

This usually means you are dereferencing a NULL pointer, or trying to
access memory outside your address space (by, e.g., dereferencing a
pointer which has a garbage value, or running out of bounds of an array). 
Use the symify program to find the source line where the disaster strikes 
you.  Symify is in your bin/ subdirectory of the main DJGPP installation 
directory.  Run your program until it crashes, and then, with the stack 
dump still on the screen, type this:

	symify progname

where `progname' is the name of your program.  You should compile your
program with -g switch and invoke symify from the directory which holds
the sources.  Symify will then print a source filename and a line number
for each address of the stack trace, so you'll see exactly what sequence
of functions calls caused the program to crash.  You will then have to
debug your program to find the way to fix the bug. 

- Raw text -