From:	frazer AT rtp DOT ericsson DOT se (Scott Frazer)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: emacs 19.34 crashes immediately on win nt 4.0
Date:	Fri, 14 Feb 1997 16:47:06 GMT
Organization:	Ericsson Data Services Americas
Lines:	34
Message-ID:	<33049571.3003328@cnn.exu.ericsson.se>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970213082031 DOT 8898G-100000 AT is> <3303886d DOT 15652352 AT cnn DOT exu DOT ericsson DOT se>
NNTP-Posting-Host:	pc093.rtp.ericsson.se
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

frazer AT rtp DOT ericsson DOT se (Scott Frazer) wrote:

>Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>
>>If you have time and motivation, please download the Emacs sources,
>>compile Emacs on your machine and try to debug this.  At this point, I

[ snip ]

>'scuse me for jumping in here, but I am also running Windows NT v4.0
>and can't get emacs to run, so I downloaded the sources and compiled
>it (after a little makefile massaging).  Oh, and I am using all the

[ snip ]

>(gdb) step
>277           _go32_dpmi_free_dos_memory (&info);
>(gdb) step
>
>Program received signal SIGSEGV, Segmentation fault.
>Fframe_or_buffer_changed_p () at dispnew.c:1942
>1942      FOR_EACH_FRAME (tail, frame)
>(gdb)
>

To follow up on my own post here ... I commented out the 
_go32_dpmi_free_dos_memory call from dosfns.c and w16selec.c
( the only two places in the 'src' and 'lib-src' directories
it exists ), and lo and behold emacs works ( so far ).  I
don't know how dangerous this is ... maybe some sort of subtle 
memory leak that will eventually kill the process.

Scott

- Raw text -