cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1998/05/26/03:37:16

From: pavenis AT lanet DOT lv
Message-ID: <B0000030801@stargate.astr.lu.lv>
To: rushfan357 AT aol DOT com (RushFan357)
Date: Tue, 26 May 1998 10:35:58 +0300
MIME-Version: 1.0
Subject: Re: VGA Degugging in RHIDE?
CC: djgpp AT delorie DOT com
In-reply-to: <1998052603095800.XAA03774@ladder03.news.aol.com>

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.

Andris

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019