Date:	Sun, 1 Jun 1997 16:06:47 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"Jason M. Daniels" <bd733 AT rgfn DOT epcc DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: Exceptions vs. Signals
In-Reply-To:	<5mkf8v$qc1@news.epcc.edu>
Message-ID:	<Pine.SUN.3.91.970601160549.24182D-100000@is>
MIME-Version:	1.0

On 29 May 1997, Jason M. Daniels wrote:

> What is the difference between a Page Fault and a SIGSEGV?

SIGSEGV is a name of the signal that is generated for quite a few
exceptions.  Page Fault is one of them; others include Stack Fault,
GPF and a few others (see the description of the `signal' library
function in the libc reference for more details).

> Why is it that 
> SIGSEGV's display more information about the error than a Page Fault 
> (most notably, a Page Fault doesn't give Call Frame Tracebacks).

The displayed info is the same in all cases.  The difference that you
observe is specific to your particular problem/bug.  For example, if
you trash the stack you (obviously) cannot expect to get a meaningful
stack dump.

> I'm 
> writing a program, and it is generating Page Faults. Due to the lack of 
> information given from this error, it is making it very hard to debug. :(

If you cannot figure things out, post the entire message printed when
the program crashes (including the registers' listing and the rest):
it might include cricual info about your problem.  If you can pinpoint
the place where it crashes, post the code fragment around there also.

- Raw text -