From: "Colin W. Glenn" Newsgroups: comp.os.msdos.djgpp Subject: Re: Q: Is it possible to use GDB debugger with Allegro? Date: Sat, 11 Jan 1997 14:26:21 -0600 Organization: Greater New Orleans Free-Net Lines: 24 Message-ID: References: <59snma$qju AT newton DOT pacific DOT net DOT sg> <8PY8kpAdqByyEw3J AT talula DOT demon DOT co DOT uk> <5aqds7$sok AT newton DOT pacific DOT net DOT sg> <32D4EA33 DOT 306E AT Mathematik DOT tu-chemnitz DOT de> <5b2vmn$ddo AT newton DOT pacific DOT net DOT sg> NNTP-Posting-Host: sparkie.gnofn.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <5b2vmn$ddo@newton.pacific.net.sg> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp On Thu, 9 Jan 1997, Victor wrote: > Robert Hoehne wrote: > >FVR wrote: > >> I found my mistake already - I was using a.exe instead of a.out (I > I'm using gdb 4.16, but with the Allegro you have just one breakpoint, > can handle .exe files, only the breakpoint has to be set very Why not use a tried and sure method of debugging as well? Use a pause statement: void pause(char *what) { /* put a cursor save and restore in */ /* the pointer is so you can pass a message like the following */ printf("%s", what); do while(!getc(stdin)); } pause("Got to point such and such") Excuse any codeing errors, I gotta a cold.