From:	j DOT aldrich6 AT genie DOT com
Message-Id:	<199607230249.AA293530157@relay1.geis.com>
Date:	Tue, 23 Jul 96 02:33:00 UTC 0000
To:	valgasu AT mv DOT mv DOT com
Cc:	djgpp AT delorie DOT com
Mime-Version:	1.0
Subject:	Re: DPMI?

Reply to message 9945457    from VALGASU AT MV DOT MV on 07/21/96 11:37PM


>Does cwsdpmi need/like a specific type of setup? (ie, no emm386 or whatever)
>I get random crashes due to faults and exceptions and stuff when I run my
>programs, and when I use symify, sometimes the only things it lists are
>not in my code at all... one example I ran into recently had it crashing
>at some offset into _djgpp_exception_table (or something close to that name)

CWSDPMI doesn't need anything special to run.  It ought to be able to
handle anything your system throws at it.  :)

As for 'random' crashes, there are a couple of possibilities:

1) Your program dereferences a NULL pointer.

2) Your program dereferences a NULL pointer with nearpointers enabled.
   This is even worse because it can seriously trash your computer.

3) You are overflowing the default 256K stack by declaring large
   automatic arrays.  You can increase the stack size by setting _stklen
   within your program or by increasing the stack with 'stubify'.

>also, sometimes I get SIGSEV and GP crashes when I'm *compiling*, ie, the
>program being run is gcc...  Regardless of how badly *I* program, I
>suspect that the wizards behind this package are doing it right :)

Do these crashes occur after your own program has crashed?  If
so, the most likely problem is that your program screwed something
up in the system before it finally died, thus messing up every other
program you run.  Try rebooting after any crash that involves GPF's,
page faults, or reports an address in _djgpp_exception_table.

That's all I can think of for now...

John

- Raw text -