Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: VolkerOth AT aol DOT com, djgpp AT delorie DOT com Date: Wed, 14 May 1997 14:34:32 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: Re: Debugging in RHIDE with CWSDPMI Content-Transfer-Encoding: 8bit Precedence: bulk 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 ? > Debugging "normal" programs (no hooking of ints etc) works, of course. I can confirm that, some things fails under CWSDPMI when debuging. I don't know if the bugs are in CWSDPMI or in the libdbg.a from the package. I think that it works in Loose95 mainly because the DPMI server is much more big and includes A LOT of tricks to workaround bugs in the clients or strange situations. One very notable example is that libc and CWSDPMI handles very bad the exit of the programs in low memory conditions. Is very common to see how the djgpp exe freezes and never goes to DOS. > I already had problems with CWSDPMI in conjunction with > LibHW, hooking the old keyboard interrupt and using the > german keyboard driver (keyb GR). This also worked in > Win95, as far a I remember. Well here the interaction with the keyboard programm is very important, remmember that M$ knows what your own programs does ;-) > Can anybody confirm my problems ? Yeap. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013