Re: Strange bug with ilisp 5.12.0 on NT

>>>>> Hannu Koivisto writes:

Hannu> Always remember to mention the version number, the type
Hannu> (XEmacs, Emacs) and the compilation method (cygwin, native) of
Hannu> your emacs as well.

Okay.  GNU emacs 20.6.1 on NT 4.

>> emacs gets into an infinite loop, consuming 100% of the

Hannu> Always?  After some specific action?
After typing M-x lispworks.


Hannu> Such "cannot be interrupted" problems are sometimes (often?)
Hannu> Emacs problems (perhaps in addition to a problem in a package
Hannu> which triggers it), 
Indeed, but in this case, the _only_ change to the environment
is migrating from ilisp 5.10.1 to 5.12.0.  Nothing else changed.
Same Lispworks image, same emacs, same additional packages.

Hanny> but in this case the many bindings of
Hannu> inhibit-quit to `t' in ILISP might cause this (that you cannot
Hannu> interrupt, that is; the reason for it being stuck is another
Hannu> question).  You could try modifying them all from inhibit-quit
Hannu> <- t to inhibit-quit <- nil and then, when Emacs/ILISP gets
Hannu> stuck, try to interrupt it with C-g.  If you are lucky, you'll
Hannu> get a backtrace (load sources instead of compiled files so that
Hannu> you can make more sense of it) and see where ILISP is stuck
Hannu> (use edebug for more precise debugging, then).

Thanks.  I'l try that.

--
			Alain Picard
			Memetrics

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm