Date: Thu, 17 Apr 1997 09:56:07 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bryan Murphy <bf461 AT cleveland DOT freenet DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: Try this one on for size
In-Reply-To: <199704162029.QAA02720@hcst.net>
Message-ID: <Pine.SUN.3.91.970417095541.18537H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 16 Apr 1997, Bryan Murphy wrote:

> Any idea where I should even START looking for this one?? :)  Other than
> the pointers, it does a little twiddling with the timer (using a Library I
> downloaded that worked fine when I tested it) and not much else.

The starting point should be the crash traceback printed when the
program dies.  Use symify to convert the traceback to human-readable
sequence of source filenames and line numbers that will tell you
exactly where the program crashed.  (The FAQ tells more about `symify'
in section 9.2.)  You should look at the source near that place and
try to figure out what's wrong there (look for wild pointers, code
that runs off array limits, etc.).  If you can't figure out by looking
at the source, run the program under a debugger and print values of
variables that seem to be connected to the crash.

If you are stuck, it might help posting the exact traceback printed at
the point of crash: it could include vital hints to the nature of the
bug.

I suggest you run all the above on MSDOS, not Windows, since it seems
that CWSDPMI catches your problem much earlier, and it will be much
easier to debug.