From:	mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Memory access
Date:	Fri, 06 Dec 1996 01:01:39 GMT
Organization:	Oxford University
Lines:	34
Message-ID:	<32a76fa7.13665439@news.ox.ac.uk>
References:	<19961205205800 DOT PAA05656 AT ladder01 DOT news DOT aol DOT com>
NNTP-Posting-Host:	mc31.merton.ox.ac.uk
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Apparently-To:	djgpp AT delorie DOT com

On 5 Dec 1996 20:56:53 GMT, isjolly AT aol DOT com wrote:

>I need to access a binary file which has been loaded into memory. When
>references to data is made in the code, using pointers to structures DJGPP
>v2 exits without crashing with the error message:
>
>  Exiting due to signal SIGSEGV
>
> General protection fault at eip=000017d2
>.....
>
>Call frame traceback EIPs:
>
>   0x000017d2
>   0x000016ba
>   0x0000155a
>   0x00001d13
>
>Can anybody help with this or suggest a way to get around it?
>I did think it was something to do with far pointers but don`t know how
>they work.

Please post your source code, if it's not too long. If it is, post the
shortest program you can which should work but doesn't.

As for solving this problem yourself, you can try typing 'symify
<exe-filename>' while the information above is still on the screen -
this will add function names to the call frame traceback, which should
give you a better idea as to what was happening when it crashed.

SIGSEGV is probably occuring because you've forgotten to initialise a
pointer / have initialised it incorrectly.

George Foot

- Raw text -