Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: pavenis AT lanet DOT lv, djgpp AT delorie DOT com, rushfan357 AT aol DOT com Date: Tue, 26 May 1998 11:28:53 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: VGA Degugging in RHIDE? In-reply-to: References: <1998052603095800 DOT XAA03774 AT ladder03 DOT news DOT aol DOT com> Precedence: bulk Andris wrote: > From: rushfan357 AT aol DOT com (RushFan357) > Subject: VGA Degugging in RHIDE? > Date sent: 26 May 1998 03:09:58 GMT > > > I'm hoping that someone could take a few minutes to help me out. > > > > I finally got the Doom Sources to compile in RHIDE 1.4 (using Allegro of > > course). > > > > My problem is that when stepping into the code in RHIDE, I crash. The debugger > > gose through all the "startup" code, but when it's time to print text to > > stdout, it bombs. > > > > I don't believe that it's my port of the sources because the .exe runs fine > > with a regular make(no modifications at all). > > > > I'm guessing that either I missed somethinbg in the documentation, or RHIDE > > doesn't support VGA (Non-Text modes). > > > > Could someone please lat me know if RHIDE does do VGA debugging & if so could > > ya' give me a "hint"? If not, could you point me to a GNUish debugger that > > does? > > I haven't tried with Allegro. But I can tell about my experience with GRX > (versions 2.2 and the following beta versions up to 2.29): > > - I have tested mostly 16 color modes and debugging from RHIDE works. > However there may be problems depending on which video card You have: > I didn't have probems with S3 Trio64, looks that there are no problems also > with ATI 3D Charger (only some days yet), but debugging under S3 Trio32 > is not very nice. This was not only problem with Trio32 > - I haven't did carefull testing with 256 and other modes. Basically RHIDE works with standard VGA modes and with VESA modes. There are problems with some video boards because of bugs in the VESA implementation, mainly in the routines that save/restore the video mode, looks like these functions are used only by few programs like RHIDE and hence they aren't very well tested. About the crash got by RushFan357: Are you using the Allegro mouse? SET ------------------------------------ 0 -------------------------------- Visit my home page: http://set-soft.home.ml.org/ or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013