Date:	Thu, 21 Nov 1996 17:26:49 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Cc:	DJGPP AT delorie DOT com
Subject:	Re: V2 again
In-Reply-To:	<F024275684@fs2.mt.umist.ac.uk>
Message-Id:	<Pine.SUN.3.91.961121172252.24365E-100000@is>
Mime-Version:	1.0

On Thu, 21 Nov 1996, A.Appleyard wrote:

> D:\HEWSON>a spex_dat\length1.spt miaow
> Exiting due to signal SIGSEGV
> Stack Fault at eip=00001b09
> eax=00050264 ebx=000501c0 ecx=00000000 edx=00050240 esi=00000054 edi=0000e6d0
> ebp=0004e620 esp=fff4e5ec program=D:\HEWSON\A.EXE
> cs: sel=00a7  base=10000000  limit=0005ffff
> ds: sel=00af  base=10000000  limit=0005ffff
> es: sel=00af  base=10000000  limit=0005ffff
> fs: sel=008f  base=00035c80  limit=0000ffff
> gs: sel=00bf  base=00000000  limit=ffffffff
> ss: sel=00af  base=10000000  limit=0005ffff
> 
> Call frame traceback EIPs:
>   0x00001b09
> 
>   What may have caused it? I was not doing anything at all with signals.

V2 supports signals.  The segmentation violation inside your program
caused a protected-mode exception that is passed to your program as a
signal SIGSEGV (so that you could define a handler for this case and do 
something other than the default handler which just aborts your program).

> How can I get this junk translated into something meaningful?, like symify
> does with the hex dump that programs compiled by v1 make when they error?

Use symify that comes with v2.  The above is the same stack trace known 
to you since v1 days, it just looks a bit different.

- Raw text -