Date: Thu, 15 May 1997 19:28:35 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Volker Oth <VolkerOth AT aol DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Debugging in RHIDE with CWSDPMI
In-Reply-To: <3379B8D1.4C29@aol.com>
Message-ID: <Pine.SUN.3.91.970515192434.10056N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Wed, 14 May 1997, Volker Oth wrote:

> I had some troubles lately debugging a program using Allegro's
> GUI (installs keyboard_handler and timer) with RHIDE in DOS.
> As I asked Robert Höhne (RHIDE) about this, he said he could
> debug my program in Win95. So I tried it and yes, it worked.
> So there is obviously something different/buggy (?) in
> CWSDPMI compared to Win95's DPMI provider, isn't it ? Hints ?

Please submit a complete report about how this fails with CWSDPMI.  I 
also suggest that you cc: your message to Charles Sandmann 
<sandmann AT clio DOT rice DOT edu>, who is the author of CWSDPMI, because he could 
explain what happens or give you hints about it.

Generally, debugging programs which hook hardware interrupts is tricky,
especially with keyboard handlers, since DJGPP itself hooks the keyboard
interrupt.  But it might be that your program or RHIDE has some subtle
bug, and CWSDPMI is less tolerant to such bugs.