Date: Mon, 18 Dec 2000 09:47:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tuukka Kalliokoski <tuukka DOT kalliokoski AT koti DOT tpo DOT fi>
cc: djgpp AT delorie DOT com
Subject: Re: Problems with LWP 2.0 / djgpp 2.03
In-Reply-To: <8i5q3t4nrnb5rig81irlasimit6qrv1pk1@4ax.com>
Message-ID: <Pine.SUN.3.91.1001218094732.15310H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 17 Dec 2000, Tuukka Kalliokoski wrote:

> >Ouch, Windows.  I'd suggest to try in DOS mode first, with CWSDPMI.
> >Windows has some nasty tricks as far as timer interrupt is concerned
> 
> Works even worse in DOS - the SIGSEGV hits immediately.

That's good.  I suggest to continue debugging in plain DOS, it will
make problems stick out.

> I think that maybe the stack frame set up by SIGILL (which the
> LWP uses as scheduling interrupt) is set up differently in the
> current djgpp version than in the one LWP was tested with.

If you can post the relevant fragments from LWP here, perhaps we could
give you some directions for untangling this riddle.