Date: Sun, 13 Oct 1996 16:54:00 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Michael Schuster <Schuster AT eev DOT e-technik DOT uni-erlangen DOT de>
Cc: djgpp AT delorie DOT com
Subject: Re: how to debug Allegro
In-Reply-To: <4AFEB5684B@merlin2.e-technik.uni-erlangen.de>
Message-Id: <Pine.SUN.3.91.961013165035.16204C-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 11 Oct 1996, Michael Schuster wrote:

> carried out on the screen, based on allegro. When I start the debugger
> gdb with "gdb program_name" and "running", it works well, the
> calculation and the writing to files. But after switching to the
> graphic-mode (autodetect, 800 x 600 Pixels) the screen shows the
> graphical surface, but the program stops, nothing is working anymore.
> So I have to quit the program with 'ctrl+alt+del'. I have no ideas,

I think the debugger doesn't stop working, it just doesn't switch the 
screen back to text mode, so you don't see the usual GDB display and 
prompt.  So what you need is a method of switching the screen to text 
mode.

An easier way might be to redirect GDB output to a printer:

	gdb myprog > prn

Did you try this?