Date: Sat, 13 Feb 1999 12:41:35 -0500
Message-Id: <199902131741.MAA26431@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <7a4bdp$1ok$1@news1.cableinet.co.uk> (jonpin@skynet.co.uk)
Subject: Re: GPF - Only in DJGPP, not TurboC++
References: <7a45ka$nnj$1 AT news1 DOT cableinet DOT co DOT uk> <7a470v$r48$2 AT news DOT luth DOT se> <7a4bdp$1ok$1 AT news1 DOT cableinet DOT co DOT uk>
Reply-To: djgpp AT delorie DOT com


>     You want me to send you the programme eh?  All 84 pages??  You wanna go
> through 4500 lines of someone elses code?  Fine by me.......
>     I thought it might be a common problem with an easy answer.

I think the expectation was that you would do some debugging yourself
first, to try to narrow down the problem and add some clues that we
could use to help you.  For example, did you get a stack trace on the
screen, or a windows popup?  If you got a stack trace, did you run
symify on it?  Did you try using gdb to narrow down the location of
the fault?  What exact error messages were printed on the screen?

Those kinds of information would make it easier for us to guess at
what might have happened in your program.  Just saying "it broke"
isn't enough for us to even guess.  Sending us an 84-page program
isn't useful either, because we won't know where to start looking in
it.