Date: Wed, 24 May 2000 13:09:46 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: AndrewJ <luminous-is AT home DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: DPMI crashes (was re: where is the source code for long file name?)
In-Reply-To: <aLDW4.89799$55.1884542@news2.rdc1.on.home.com>
Message-ID: <Pine.SUN.3.91.1000524130930.13642E-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 Tue, 23 May 2000, AndrewJ wrote:

> But lo and behold, every time I tried to assemble a file using NASM
> from within Make, it faulted on me for no apparent reason.

Please describe the fault in more detail.  What exactly happened?

> Have you heard about this before?

Was NASM compiled with Watcom, per chance?  Did it use PMODE as its
DPMI host?  If so, this is a known issue with Watcom-compiled
programs: they crash when run from DJGPP programs, evidently because
the Watcom executable in conjunction with PMODE hooks the DPMI Int 31h,
but never unhooks it on exit.  So the DPMI interrupt is left pointing
to void, and there's no escape or work-around, since even to hook the
interrupt again, you need an Int 31h call.

NASM compiles with DJGPP, so you can simply use a DJGPP-compiled
version instead.

> I'm going to see if I can get it to do it again so I can give some
> more detailed information.

Yes, please.  A crash traceback and registers would be most welcome.