From: fesenko AT pacific DOT net DOT sg (Victor)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Question about debugging
Date: Sat, 01 Aug 1998 05:03:57 GMT
Organization: Subscriber of Pacific Internet, Singapore
Lines: 23
Message-ID: <35c2a1b6.15705785@news.pacific.net.sg>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980728104439 DOT 4133B-100000 AT is> <p6tu3429of4 DOT fsf AT SunKEDR30 DOT inp DOT nsk DOT su> <p6tr9z69mrc DOT fsf AT SunKEDR30 DOT inp DOT nsk DOT su>
NNTP-Posting-Host: dyn111ppp229.pacific.net.sg
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I'd like to thank everyone who responded to my request for help.
I've found the problem and it was (not surprisingly) a bug in some
another routine which overflowed a global array and consequently
overwrote the stretch_blit(). This is my guess, because I presume it
would take a long time to find out what really happened there, but
once I fixed that bug, everything was running fine.
And I find Eli's elaboration on the traceback very insightful.
I think it would be a good idea to make a small guide to the values of
registers and other information on the traceback. This could help a
lot to the people who find themselves staring in dispair and disbelief
on the traceback of otherwise very nice program.
The fact is that this information is available, but it is hidden very
deeply in different help files, manuals, etc.
For example, it took me ages to find out that the allegro library file
has to be recompiled with DEBUGMODE option, to get the proper
traceback. And this is not because this info isn't available (it is
actually, of all places, in allegro.txt file), but I wasn't looking
there for it. I managed to stumble on it after long hours of going
through mail archives.
I think I'll start this and I beleive there are many people who can
contribute to it from the point of view of their area of expertise.

Victor.