From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Problem with DOS and DPMI Date: Sun, 31 Oct 1999 10:05:45 +0200 Organization: NetVision Israel Lines: 26 Message-ID: References: <7vf5qm$i4i$1 AT front1 DOT grolier DOT fr> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 941357062 11145 199.203.121.2 (31 Oct 1999 08:04:22 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 31 Oct 1999 08:04:22 GMT X-Sender: eliz AT is In-Reply-To: To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 31 Oct 1999, Damian Yerrick wrote: > > Page Fault cr2=10000000 at eip=e75; flags=6 > > eax=00000030 ebx=00000000 ecx=0000000c edx=00000000 > > esi=0001a44a edi=00000000 ebp=00000000 esp=00002672 > > cs=18 ds=38 es=af fs=0 gs=0 ss=20 error=0002 > > ================================================ > > Page Fault in Sandmann's CWSDPMI not in Micro$oft's DPMW32 > > This means you are accessing an address below 0x00001000. Not in this case. This message comes from CWSDPMI, not from the application (the latter never prints cr2 and flags, and the segment registers are printed differently). Section 12.2 of the FAQ describes the application crash message when dereferencing NULL pointers; you will see that the format is different. > Run symify on > the traceback (should be below the register dump) and see if you can > pinpoint the error. The crash message of CWSDPMI doesn't include the traceback, and even if it would, it won't help you anyway, since CWSDPMI is not a DJGPP executable. So SYMIFY can't help here.