Date:	Thu, 1 Oct 1998 13:56:11 +0200 (MET DST)
From:	Olivier Perron <perron AT art DOT alcatel DOT fr>
X-Sender:	perron AT rtbsci146s
To:	Helge Waastad <hwa AT pax DOT priv DOT no>
Cc:	djgpp AT delorie DOT com
Subject:	Re: sigsegv problems....
In-Reply-To:	<01bded24$67a9aaa0$0a016464@hwa>
Message-Id:	<Pine.GSO.4.05.9810011351380.11116-100000@rtbsci146s>
Mime-Version:	1.0

On 1 Oct 1998, Helge Waastad wrote:

> When I run my program, I get this error message:
> 
> 			Exciting due to signal SIGSEGV avsluttet.
> ----------------------------------------------------------------------------
> ----
> Page fault at eip=00006efc, error = 0004
> eax=00014920	ebx=00000020	eex=00054ab2
> edx=00000020 eci=00000054	edi=0001487c
> ebp=00054a98	esp=00050a80	program=c:\tc\cfiles\test.exe
> 
> cs: sel=00a7	base=10000000	limit=000dffff
> ds: sel=00a7	base=10000000	limit=000dffff
> es: sel=00af	base=10000000	limit=000dffff
> fe: sel=008f	base=000069f0	limit=0000ffff
> gs: sel=00bf	base=00000000	limit=ffffffff
> ss: sel=00af	base=10000000	limit=000dffff
> 
> call frame trackback EIPS:
> 0x0000befc
> 0x00002763
> 0x000016ae
> 0x00002e26
> 
> I wonder if this is a memory problem, but I'm not sure.
> Does anyone know the solution to this error message??
> 
> hw
> 
Compile your program with the -g switch, run your program again and when
the traceback appears on the screen, run: symify <your program name>.
symify will automagically show you which line of your code triggs the
sigsegv.
Then look at your code to find why the sigsegv occured (certainly a memory
problem like dereferencing a NULL pointer or going behind the bounds of an
array, etc...)

- Raw text -