🚀 go-pugleaf

In article <1992Oct30.150221.20511@ryn.mro4.dec.com> verma@pfeast.enet.dec.com (Virendra Verma) writes:
>
>Hi every one. I have problem debugging a large program using TD386 (virtual
>debugging). The message I get is "Unexpected interrupt 0D". Some times I 
>get Exception 13. The manual says that program's memory is overwritten by 
>some other program. The problem still persists after disabling MOUSE driver, 
>ANSI.SYS, SETVER, DOSKEY and any other program which I normally use. My 
>system configuration is as follows:
>
>	486 DX with 8 MB of memory with no expanded memory manager. Do I
>	need one?
>	MS DOS 5.0 with Borland C++ V3.1
>
>	Size of my program 360959 bytes.
>	Compiled with huge memory model.
>
>	Installed drivers HIMEM and TDH386 drivers.
>
>Another clue: The point of failure for program with large memory model is
>different than that with huge memory model.
>
>Thanks in advance for any help.
>


Sounds like a pointer problem to me. Making a jmp, or call, or an int vector
pointing to an offset of 0FFFFH, will cause a real mode and v86 mode
protection violation. Additionally, making a word or greater access
at offset 0FFFFH will also cuase a real mode or v86 mode protection
violation. Another culprit - poping an IP of FFFFH off the stack.
Stack corruption comes in many flavors and can be difficult to find.



Cheers!
Steve



-- 
-----------------------------------------------------------------------------
"Ain't it hard when you're all alone in the center ring, now there's no
time left to borrow." - Eagles, "Desperato (reprise)"
-----------------------------------------------------------------------------