From:	"Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Exceptions, worked _before_ GCC 2.8.1. Now don't! - TEST8.CC [1/1]
Date:	Wed, 27 May 1998 13:54:50 -0700
Organization:	Hewlett-Packard, Roseville
Lines:	31
Message-ID:	<6khuif$ori$1@rosenews.rose.hp.com>
References:	<bWLoegW7sFse-pn2-5Gd3tyue1DR1 AT portA16 DOT Generation DOT NET>
NNTP-Posting-Host:	ros51675cra.rose.hp.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> The error occures (depending on how you walkthrough the source-code)
>at different points in SLList_Init... They all report a classic
>SIGSEGV error..
Try using gdb.

> Sorry for attaching files
You should be.

> but it is the only way in this case..
No its not.  First make sure there isn't a bug in your code.  Do this by

1) Compile and link with debugging enabled.  Add -g to command line or
better -gstabs.
gcc -gstabs -o foo.exe foo.c

2) Load your program into gdb
gdb foo.exe

3) Run the program (add any arguments after typing 'r')
r

4) Wait for the program to crash.  You should now be able to type 'bt' for a
backtrace, and to investigate what exactly went wrong by inspecting
variables.

Andy

- Raw text -