Date: Wed, 4 Apr 2001 16:18:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Stromberg <eplmst AT epl DOT ericsson DOT se>
cc: djgpp-workers AT delorie DOT com
Subject: Re: That crash message from the core dumper.
In-Reply-To: <200104041151.NAA12435@lws256.lu.erisoft.se>
Message-ID: <Pine.SUN.3.91.1010404161302.26435E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 4 Apr 2001, Martin Stromberg wrote:

> Shouldn't the limit on _dos_ds selector be 0x10ffef (or possibly
> 0x10fff0, I'm not sure if the limit includes the last address or not)
> instead of 0x0010ffff?

(The limit is size minus 1.)

No, 0x0010ffff is right.  setup_core_selector (on crt1.c) says:

  __dpmi_set_segment_limit(_dos_ds, 0x10ffff);

> The signal was SIGSEGV. Isn't that number 11? Still the next line from
> the core dumper says "signal: 14"? Huh?!

That number is actually an exception number, not a signal number (the 
message is misleading).  SIGSEGV's number in DJGPP is 291, not 11 as on 
most Unix systems; see signal.h.

Exception 14 (0E in hex) is Page Fault.  dpmiexcep.c maps several 
exceptions including Page Fault to SIGSEGV.