Message-Id:	<199908230657.JAA29016@ankara.Foo.COM>
From:	"S. M. Halloran" <mitch AT duzen DOT com DOT tr>
Organization:	User RFC 822- and 1123-compliant
To:	djgpp AT delorie DOT com
Date:	Mon, 23 Aug 1999 11:04:28 +0200
MIME-Version:	1.0
Subject:	Re: SIGSEGV run-time error
In-reply-to:	<09920fb9.db3bb3b7@usw-ex0108-057.remarq.com>
X-mailer:	Pegasus Mail for Win32 (v3.12)
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 22 Aug 99, wriska was found to have commented thusly:

> I am working on a program, and when I run it, I am getting 
> a SIGSEGV signal.  Does anyone know what this signal 
> means?  Any help would be greatly appreciated.  Please 
> email me with whatever help you can give me.

This processor exception means you are trying to access memory that is 
forbidden to your application.  It is always (or at least 99 in 100 times) the 
result of failing to initialize a pointer to memory properly.

Find the source code line that is causing the problem:  using a debugger will 
bring you to the stopping point.  Look at all the variables on that source code 
line that could be the problem, namely, look for a variable that is a pointer.  
Check the value of the pointer(s) on that line just prior to stepping into the 
exception.  Try accessing the pointer through indirection:  it should give you 
values you expect if you have initialized.  If the pointer itself has a value 
of '0x0', namely NULL, and you have de-referenced it in the offending line, 
that's a sure clue.

> Thank you,
> wriska


Mitch Halloran
Research (Bio)chemist
Duzen Laboratories Group
Ankara       TURKEY

- Raw text -