Message-ID: <D1FB30BBA491D1118E6D006097BCAE39263F9B@Probe-nt-2a.Probe.co.uk>
From: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: wierd problem in Allegro 3.0
Date: Tue, 14 Apr 1998 15:35:58 +0100
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Count Razumovsky writes:
> All my programs compile and link fine but when I try to run the 
> executable the program dies and I get this message:
> 
> Shutting down Allegro
> Exiting due to signal SIGSEGV
> Page fault at eip=000028b8, error=0004

This message is nothing to do with Allegro: it is produced by the
djgpp runtime library. SIGSEGV means that you triggered a segmentation
violation, ie. that you tried to use some illegal memory addresses.
Most likely this means that you are dereferencing a NULL pointer,
forgetting to allocate some memory, or writing past the bounds of
an array, but it could be almost any memory-related error or 
corruption problem. The solution is to debug your program and find
out where it is going wrong: either use a proper debugger, or run
the symify utility after you get this traceback to find out where 
the crash is occuring.

	Shawn Hargreaves.