Date:	Mon, 5 Apr 1999 08:09:32 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc:	djgpp AT delorie DOT com
Subject:	Re: LONG: My INT31 handler isn't feeling too swell
In-Reply-To:	<7e7j4e$cr4$4@news.luth.se>
Message-ID:	<Pine.SUN.3.91.990405080755.23822H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 4 Apr 1999, Martin Str|mberg wrote:

> Just tell me how to debug a interrupt handler.

Try `cprintf', or even `cputs' (since the former might call `malloc' 
which might issue a DPMI call).  I usually don't trust DOS debuggers 
anyway when it comes to a sufficiently complex program, let alone an 
interrupt handler. 

> : Why did you need to spawn Bash?  I suggest to try COMMAND.COM first,
> : since Bash does some very complex tricks with DPMI functions.  It's
> : better to begin at the first grade...
> 
> Ehum, yes; but then the bug which the program is supposed to work
> around doesn't manifest itself

Since you have now a bug in the handler itself, it's probably better
to debug it before turning to the Windows bug.  To debug the handler,
you don't need to see the Windows bug, just to have a program that
issues DPMI calls.  Any DJGPP program that runs from COMMAND.COM will
do that.

- Raw text -