Date:	Thu, 16 May 1996 16:06:35 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Francisco Gochez <arcanix AT pop DOT erols DOT com>
Cc:	djgpp AT delorie DOT com
Subject:	Re: Bugs in CWSDPMI and FSDB
In-Reply-To:	<4nar1t$5sm@news7.erols.com>
Message-Id:	<Pine.SUN.3.91.960516160040.5771F-100000@is>
Mime-Version:	1.0

On 14 May 1996, Francisco Gochez wrote:

> I've encountered a bug in FSDB and one in CWSDPMI.  Under FSDB, I was 
> debugging one of my programs (uhh.. really!), when I got to a function 
> that puts the computer in graphics mode 0x13.  As I executed the 
> instruction, the screen went black and after a few seconds, I got kicked 
> out to DOS with a register dump (sorry, I don't have the dump).

FSDB does not support debugging of graphics programs.  It just blindly 
assumes that the text screen is always visible.  If you need to debug 
graphics, you will need to change FSDB to make it switch the screen into 
the text mode when it hits a breakpoint.

> Whenever I run something that uses CWSDPMI, and then I enter Win 3.1 (no, 
> CWSDPMI is not resident at this time), I get a high-pitched sound and my 
> computer reboots (!!).

Please post the complete details of your system configuration.  It is 
very hard to make anything out of reports that don't say at least that 
much.  Most users (me included) don't have these problems, so it must be 
dependent on some peculiarity of the system configuration.

>  Also, I tend to get kicked out of FSDB with a 
> register dump (not sure which error) quite often.

Is this under Windows or in plain DOS?  Can you describe the 
circumstances under which that happens, like any specific operation you 
do in your program?

- Raw text -