From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200005061023.MAA24063@father.ludd.luth.se>
Subject: Re: The new CWSDPMI
In-Reply-To: <10005042044.AA15708@clio.rice.edu> from Charles Sandmann at "May 4, 2000 03:44:18 pm"
To: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Date: Sat, 6 May 2000 12:23:01 +0200 (MET DST)
Cc: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

According to Charles Sandmann:
> > I have managed to compile it so what option/#define is it that I should
> > use to get relevant feedback?
> 
> It depends a lot on what you are trying to diagnose.  If the problem is
> reproducible seeing calls to the DPMI provider is interesting (check out
> comment and/or defines in exphdlr) - if it's a virtual memory management
> issue enabling messages in paging.c is useful.

Well the case was hangs and the very strange crash I mailed about.

But after I compiled with -DVERBOSE and -DDIAGNOSE and haven't had any
strange crashes (almost done compiling whole djlsr203.zip), which
makes me confused.

> Sorry, I've been really busy with work and family.

On djgpp-workers (I think) we do not see the need to apologise for
this. We are aware of the higher priorities people have (like real
life).


Right,

							MartinS