Xref: news2.mv.net comp.os.msdos.djgpp:5707
From: DHGW39B AT prodigy DOT com (Eric Domazlicky)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: fsdb graphic debugging problem
Date: 7 Jul 1996 03:44:35 GMT
Organization: Prodigy Services Company  1-800-PRODIGY
Lines: 14
Distribution: world
Message-ID: <4rnbr3$23mu@usenetz1.news.prodigy.com>
References: <4r2go0$2l1m AT usenetz1 DOT news DOT prodigy DOT com> <31ded969 DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host: 192.168.254.73
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>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.
That would definetly explain my problems....thanks for the info, 
hopefully someday someone will be able to fix this, a bit too heavy for 
me. But I really thought it strange that the debugger didn't do this 
because I saw in the code where it actually did replace interrupt 9 every 
time the program swapped out, it seems to me this would fix the problem 
but obviously it didn't can you shed some light on why it wouldn't?