Xref:	news2.mv.net comp.os.msdos.djgpp:5702
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: fsdb graphic debugging problem
Date:	Sat, 06 Jul 1996 16:23:53 CDT
Organization:	Rice University, Houston, Texas
Lines:	8
Message-ID:	<31ded969.sandmann@clio.rice.edu>
References:	<4r2go0$2l1m AT usenetz1 DOT news DOT prodigy DOT com>
Reply-To:	sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host:	clio.rice.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> I am really having problems debugging my graphics/ keyboard interrupt 
> using program with the version of FSDB meant to debug these kinds of 

You should know that all the V2 debuggers disallow hooking hardware
interrupts, so if your program goes into a loop waiting for one, it will
never see one.  You can get the source to the debuggers and modify
dbgcom.c to do what you think needs to be done.  I never completed the
toggling of the HW interrupts.

- Raw text -