delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/02/13/00:25:11

From: Daniel Barker <sokal AT holyrood DOT ed DOT ac DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: EMACS and/or Windows 98 crash
Date: Sat, 13 Feb 1999 05:18:26 +0000
Organization: Edinburgh University
Lines: 114
Message-ID: <Pine.GSO.3.95.990213051250.15150B-100000@holyrood.ed.ac.uk>
NNTP-Posting-Host: holyrood.ed.ac.uk
Mime-Version: 1.0
X-Trace: scotsman.ed.ac.uk 918882972 12742 129.215.38.17 (13 Feb 1999 05:16:12 GMT)
X-Complaints-To: usenet AT scotsman DOT ed DOT ac DOT uk
NNTP-Posting-Date: 13 Feb 1999 05:16:12 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

The crash was on exiting DJGPP EMACS 19.34, from FILES menu / Exit
Emacs.

I typically run a compute-intensive Win32 CLI application called LVB for a
few days, during which I use EMACS heavily, DJGPP ports of GNU tools such
as RCS, LESS and GCC, also Ensemble CD and occasionally Windows 98 dial-up
connection software, Telnet, FTP, Internet Explorer, Excel, PowerPoint,
YAP and GS View. I asusme due to some resource leak, the computer
typically gets slower and slower, becoming almost unbearable after about a
week without re-boot. Perhaps there is a memory leak, since allocated
memory gets higher and higher, according to System Monitor. However, the
computer was running fast at the time of this crash, because little other
than LVB had been run since the last boot. Only recently had the 64 MB of
physical RAM been used up, probably following brief use of Excel. None of
Telnet, FTP or Internet Explorer had been used since the previous boot
almost 3 days ago, because, when the computer was last switched off, I had
put the it so far from the phone socket that connection was impossible
with my cable.

Dr Watson for Windows 98 was running and generated a snapshot for the
time of the crash. Selected extracts follow. I would be happy to send
the whole snapshot file to anyone who would like to see it, as an
e-mail attachment.


Diagnosis:

Combined VGA/DIB 386 enhanced mode display component attempted to
access memory that does not exist.

Module Name: vgafull.3gr
Description: Combined VGA/DIB 386 enhanced mode display component
Version: 4.10.1998
Product: Microsoft(R) Windows(R) Operating System
Manufacturer: Microsoft Corporation

Application Name: WINOA386.MOD
Description: Non-Windows application component for 386 enhanced mode
Version: 4.10.1998
Product: Microsoft(R) Windows(R) Operating System
Manufacturer: Microsoft Corporation


System:

Microsoft Windows 98 4.10.1998
Upgrade using CD

IE 4.0 4.72.3110
Uptime: 2:22:01:42 Normal Mode


Computer:

GenuineIntel Pentium(r) Processor
64 MB RAM


Resources:

90% system resources free
Windows-managed swap file on drive C (556 MB free)
Temporary files on drive C (556 MB free)


Tasks:

Program      Version     Type

Kernel32.dll 4.10.1998   4.3
MSGSRV32.EXE 4.10.1998   4.0
Mprexe.exe   4.10.1998   4.0
MMTASK.TSK   4.03.1998   4.0
Wgfe95.exe               3.1
Mstask.exe   4.71.1769.1 4.0
Explorer.exe 4.72.3110.1 4.0
Systray.exe  4.10.1998   4.0
Point32.exe  12.00       3.1
Taskmon.exe  4.10.1998   4.0
Drwatson.exe 4.03        4.0
MS-DOS       4.10.1998   MS-DOS
Lvb.exe                  4.0
Spool32.exe  4.10.1998   4.0
MS-DOS       4.10.1998   MS-DOS
CTCD.EXE     1.1         3.1


MS-DOS Drivers:

HIMEM
EMM386
DBLBUFF
GUARD
KEYB
IFSHLP
DOSKEY


Details:

Command line: "C:\WINDOWS\Desktop\Emacs.PIF"

Trap 0e 0004 - Invalid page fault


Daniel Barker,
Institute of Cell and Molecular Biology,
Swann Building,
King's Buildings,
Mayfield Road,
Edinburgh
EH9 3JR
UK

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019