Date: Mon, 13 Dec 1999 10:36:45 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "regis.dupuy" <regis DOT dupuy AT wanadoo DOT fr>
cc: djgpp AT delorie DOT com
Subject: Re: newbie debugging need help
In-Reply-To: <830ul9$s56$1@wanadoo.fr>
Message-ID: <Pine.SUN.3.91.991213103600.29470N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 12 Dec 1999, regis.dupuy wrote:

> when I debug c programs, wich use allegro, with rhide, I've got many
> problems
> for example the windows of the source become very small and it becomes
> impossible to read
> also it often crash

Make sure you use the latest version of RHIDE.

Switch your Windows session to full screen.

> is it possible to debug correctly with rhide or must I use an other debugger
> ? (directly the one that rhide call for example if yes how must I do )

You could download and install GDB 4.18 (v2gnu/gdb418b.zip) and use
that, since it solves several serious bugs, and is based on a much
better version of DJGPP debug support routines, that could matter if your 
program hooks interrupts.  (RHIDE's built-in debugger is just GDB with 
the user interface removed.)  But GDB is not a full-screen debugger, and 
using it to debug graphics programs is not very convenient.