Re: [h-e-w] Some issues with ntemacs 21.1

[Tim Van Holder]

Theodore Jump wrote:

> At 01:29 PM 11/12/2001 +0100, Tim Van Holder wrote:
>
> > * ntemacs 21.1 chokes on loading term/w32-win.el; it gets an access
> >   violation due to trying to read address 0x00000020.
> >   IIRC the x-close-connection stuff (around line 1147) is what
> >   triggered it.
>
>
> Some particulars may be helpful here, you've not given anyone much to go 
> on in trying to help you out. Since I know from first-hand experience 


I think I was quite specific: if term/w32-win.el is loaded, emacs crashes:
  The instruction at "0x010c8ab8" referenced memory at "0x00000020".
  The memory could not be "read".

I tried using eval-region to locate the exact problem; this is how I
know that it's the x-open-connection call in the 'if' on line 1147 that
causes it.
This happens under Win2K SP2 and NT4 SP 6.

> that NT Emacs 21.1 CAN work fine on Windows Me, 2K, XP, and NT4 I have 
> doubts that it is Emacs alone that is causing the problem, but rather 
> likely some interaction with either your os configuration or other 
> software on your machine.


I'm sure it does usually run nicely.  But it happens on my customized 
home PC as well as on the out-of-the-box Dell machines at work, so an 
external issue seems unlikely.

> Does this happen when you run it as "emacs -q" for example?

Yup, tried that: ran emacs -q, opened term/w32-win.el and did 
eval-buffer: crash.
Same with (load-library "term/w32-win").