Message-ID:	<358A81B7.E2D7808F@post.comstar.ru>
Date:	Fri, 19 Jun 1998 19:20:23 +0400
From:	Dim Zegebart <zager AT post DOT comstar DOT ru>
Reply-To:	zager AT post DOT comstar DOT ru
Organization:	Comstar Ltd.
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	Alberto Chessa <achessa AT fiar DOT finmeccanica DOT it>, djgpp AT delorie DOT com
Subject:	Re: [Allegro] lwp crash ?
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980618191028 DOT 25930E-100000 AT is>

Eli Zaretskii wrote:

> On 15 Jun 1998, Alberto Chessa wrote:
>
> > My Allegro based program crash when running under DOS+CWSDPMI. It works
> > fine under Win95 and seem to be bug free (a bad pointer reference should
> > produce some strange effect either unser Win95).
>
> No, Windows 95 doesn't catch null pointer dereferences, so it lets your
> program run.  But CWSDPMI catches such atrocities and aborts your
> program.
>
> > Symify report a page fault at line 572 lwp.c.
> >
> > Any ideas ?
>
> I have an idea: debug your program starting at line lwp.c.  You have a
> bug.

 Send me your copy of lwp.c and I try to help you (I don't know which version
of LWP are you runnig).
BTW, from my expirience with LWP such things happens then you write behind
allocated lwp-stack.
For example, you run self-recurrent  function, or call too many sub-functions
with large number of parameters.
So, first suggestion - increase stack size then you do lwp_spawn(...) and see
what changes.

--
____ ____
|   \   /   Dim Zegebart
____/____

Moscow Russia
WWW - http://www.geocities.com/siliconvalley/pines/7817
DZcomm - comm library for Allegro
Palantir - multitasking kernel for Allegro (based on PDMLWP)

- Raw text -