Xref: news2.mv.net comp.os.msdos.djgpp:5713
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: fsdb graphic debugging problem
Date: Sun, 07 Jul 1996 12:15:53 CDT
Organization: Rice University, Houston, Texas
Lines: 15
Message-ID: <31dff0c9.sandmann@clio.rice.edu>
References: <4rnbr3$23mu 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

> 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?

Let's just say my time to work on DJGPP V2 over the last 2 years has been
about 1/4 what I had originally planned - so many things which should have
been completed never made it.  HW interrupts, signals, and FPU emulation
in the debuggers never made it off the design notepad due to lack of time.
Debugging them is a bitch, since it needs to be done on a ram disk just
in case you forget to save a register and trash DOS, and each messup is
a reboot.  I have a copy of ldbg ported to V2 which is in limbo due to
a legal naming mess, so I haven't done anything with it other than let
it sit.  I know it allows serial port debugging.  I don't remember where
I put it ...