At 05:00 PM 4/26/2004 -0400, Patrick J. LoPresti wrote:
>Michael Devore <[EMAIL PROTECTED]> writes:
>
>> First thing to look at is the register values, which are across the
>> top line.  We need those values.  Then look at the failing CPU
>> instruction line which is highlighted in the main window.  That
>> together with the register values should give the immediate reason
>> for failure.  The EFL flags value right above the main window would
>> be good info to know, too.
>
>OK, here we go.  Registers:
>
>EAX 00007D6C  EBX FFFF0808  ECX 00000003  EDX 00002636
>ESI 00047D6D  EDI 000008C8  EBP 000008C6  ESP 000008CC
>
>EIP 0357  CS 0005  SS 00CF  DS 2147  ES 2B5F  FS 0000  GS 0000
>CR0 0012  CR2  0000
>
>Flags:  EFL 00230112
>
>Faulting instruction:
>
>  0005:0357 6300  ARPL [BX+SI],AX
>
>When I do "D 40:7B <enter>", the first byte of the hex dump is 14.

Shucks, I figured that would happen.  You're already blown out of the water by the 
time it hits the illegal opcode, trying to execute low memory data or stack as code.  
Flags are awfully interesting, though.  Looks like you're flagged as running under 
virtual mode.  Is this without EMM386 loaded?  If without, can you look at the value 
after EFL flags and see if it says RM or VM?

If you're not under EMM386 and you're getting a VM flag, it indicates they are doing 
their own V86 memory management.  That would be unexpected.  Stack values on the right 
would be useful about now, since we may need to backtrace, but first we should look at 
the instructions immediately preceding the failed one, make sure we're buried in 
non-code.

Follow-ups best to e-mail.




-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to