Message-Id:	<199607221923.MAA01698@bluesky.com>
Comments:	Authenticated sender is <kbaca AT bluesky>
From:	"Kevin Baca" <kbaca AT skygames DOT com>
Organization:	BlueSky software
To:	djgpp AT delorie DOT com
Date:	Mon, 22 Jul 1996 12:26:30 +0000
Subject:	Re: Allegro and debugging.
Reply-to:	kbaca AT skygames DOT com

> Date:          Sun, 21 Jul 1996 08:50:43 +0200 (IST)
> From:          Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
> To:            Raja Vallee-Rai <kor AT cs DOT mcgill DOT ca>
> Cc:            djgpp AT delorie DOT com
> Subject:       Re: Allegro and debugging.

> 
> On Thu, 18 Jul 1996, Raja Vallee-Rai wrote:
> 
> >    I just tried using gdb to debug a game of mine which I've
> > recently ported to DJGPP + Allegro.  Now, I'm using 
> > Allegro's keyboard handler, and it seems that the debugger
> > gobbles up all the keystrokes, thus they never get to 
> > the handler. 
> > 
> > Is there any way around this?  Anybody have any suggestions?
> 
> Suggestion: read the FAQ.  It explains in section 12.9 that you cannot 
> debug a program that hooks the keyboard interrupt.  This is a basic 
> limitation of the current debug support under DJGPP.
> 
> The latest version of the DJGPP FAQ list is available as v2/faq201b.zip 
> from the same place you get DJGPP.
> 
> 

If you chain the real mode handler to your new handler you can still 
debug.  We do this in debug versions of our code and then unchain the 
real mode handler in release versions.

-Kevin

- Raw text -