Date:	Mon, 12 Jan 1998 11:19:16 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Olavi Hytt <olaferno AT usa DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: debugger and exception, help needed
In-Reply-To:	<69atvo$4c9$1@kadri.ut.ee>
Message-ID:	<Pine.SUN.3.91.980112111858.1820D-100000@is>
MIME-Version:	1.0

On Sun, 11 Jan 1998, Olavi Hytt wrote:

> I tryed a debugger too, and after running the program some times it says:
> exception 14, error code 0x4.

Exception 14 (0Eh) is Page Fault, meaning that you are trying to
access an invalid address, like via uninitialized or corrupted
pointer.  Error code 4 means that you were trying to read that
address, not write to it.

> This is of course very much info, but there was no button on my
> keyboard to print the explanation of this error.

Didn't the debugger also say at which address/function did that
exception happen?  If it did, you need to debug near that point to
find the reason for the problem.  If it did not, try stepping through
the code until you get the exception--then you know where does it
happen.  

> Could someone say, which files in djgpp 150 megs dos archive are
> explanations of exception 14 and error code 0x4?

None.  The description of the x86 exceptions and the various
associated error codes is not DJGPP-specific, and is therefore beyond
the scope of DJGPP.  It is also something that cannot be explained
compactly (it takes a medium-size book to describe).  Try one of the
existing Intel manuals.

> Strange is too, that this error happens randomly and not after every program
> run.

Bugs are often strange, until you solve them.

- Raw text -