Date: Mon, 13 Sep 1999 12:29:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Josh Reed <obitus AT uswest DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Program Crash
In-Reply-To: <37D870DF.1E8EA1F9@uswest.net>
Message-ID: <Pine.SUN.3.91.990913122902.8713H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 9 Sep 1999, Josh Reed wrote:

> Exiting due to signal SIGILL
> Invalid Opcode at eip=00001600
> eax=00000001 ebx=00008440 ecx=00000000 edx=00000000 esi=00000054 edi=000100f0
> ebp=2a2e2a5c esp=0008f678 program=C:\JOSH_S~1\DJGPP\BIN\AUDIT.EXE
> cs: sel=00a7  base=843ff000  limit=0009ffff
> ds: sel=00af  base=843ff000  limit=0009ffff
> es: sel=00af  base=843ff000  limit=0009ffff
> fs: sel=0087  base=00007040  limit=0000ffff
> gs: sel=00bf  base=00000000  limit=0010ffff
> ss: sel=00af  base=843ff000  limit=0009ffff
> App stack: [000900f0..000100f0]  Exceptn stack: [0000ffd8..0000e098]
> 
> Call frame traceback EIPs:
>   0x00001600   _scan__FPc+112, line 43 of audit.cpp

Look at EBP: it's trashed (the normal values are inside the limits
printed under "App stack").  Some code in your program have
overwritten the stack, perhaps by overrunning the limits of some local
array.  You will have to poke around with a debugger and find out
which part of your code does this.