From: bdarnell AT vnet DOT net (Ben Darnell)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: how to debug Allegro
Date: Sat, 19 Oct 1996 01:59:16 GMT
Organization: Vnet Internet Access, Inc.
Lines: 38
Message-ID: <549cho$cdf@ralph.vnet.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 961013165035 DOT 16204C-100000 AT is>
NNTP-Posting-Host: vts-char6-s10.vnet.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> was overheard mumbling incoherently
about Re: how to debug Allegro:


>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?

also, if you call install_keyboard(), then gdb can't see what you
type.  I don't know any way around this, unless you could connect two
pc's with a null modem and do something like
	gdb myprog < com1 > com1
to redirect stdin and stdout to a different computer. (anyone out
there tried that?)


     __                         __
 /> /_ /| /   /\  /|  />  /| / /_ /  /
/> /_ / |/   /_/ /-| / \ / |/ /_ /_ /_
http://users.vnet.net/bdarnell
bdarnell AT vnet DOT net