From: fesenko AT po DOT pacific DOT net DOT sg (FVR)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: Is it  possible to use GDB debugger with Allegro?
Date: Tue, 07 Jan 1997 00:40:13 GMT
Organization: A user of Pacific Internet
Lines: 25
Message-ID: <5aqds7$sok@newton.pacific.net.sg>
References: <59snma$qju AT newton DOT pacific DOT net DOT sg> <8PY8kpAdqByyEw3J AT talula DOT demon DOT co DOT uk>
NNTP-Posting-Host: max82ppp69.pacific.net.sg
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk> wrote:

>>I tried to debug a program written using Allegro graphics library, but
>>it doesn't work (my computer goes into a deep coma, and even
>>Ctrl-Alt-Del doesn't help).

>Really? It works better than that for me. When your program hits a
>breakpoint you'll need to switch to text mode (type "system mode co80"),
>but after doing that I can single-step through Allegro programs without
>any problems. The problem comes when you want to resume execution -
>there is no way to restore the screen state, and gdb also seems to
>remove Allegro's keyboard and timer interrupt handlers, although I
>haven't properly investigated this.

I found my mistake already - I was using a.exe instead of a.out (I
thought a new version of GDB could handle .exe files ;-))
But if I try to continue execution after a breakpoint - it dies the
same way all right (I think it's not a major problem - the program can
be started from the beginning anyway).

Thanks for your help and your hint about text mode is quite helpful.

Victor Fesenko
fesenko AT pacific DOT net DOT sg