From:	"Alberto Chessa" <achessa AT fiar DOT finmeccanica DOT it>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Help POSTED BEFORE
Date:	17 Jun 1998 07:28:38 GMT
Organization:	Telecom Italia Net
Message-ID:	<01bd99c1$d4f7f640$92c809c0@chessa>
References:	<1998061618464300 DOT OAA14797 AT ladder03 DOT news DOT aol DOT com>
NNTP-Posting-Host:	a-mi23-62.tin.it
Lines:	19
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

SRotherSN <srothersn AT aol DOT com> wrote in article
<1998061618464300 DOT OAA14797 AT ladder03 DOT news DOT aol DOT com>...
> I posted a few days ago about some help with djpgg and wondering if my
machine
> could handle it..
> 
> A few asked for some more info so here goes...
> 
> this is the response to gcc -o hello.c -o hello.exe
> exiting due to signal sigsegv
> page fault at eip=0000b9ea,  error=00006 [...]

It seem you use bad pointers. Have You just try a debugger ? And symify ?
Symify has to be executed just after the crash (when the stack dump still
on the screen) and will report the symbolic entries of your stack
traceback. You shoud be able to identify the offending routine:
	symify <your-program-name>

(I discover symify just few day ago!  -- thanks to newsgroup)

- Raw text -