Problems with Emacs
Charles Plager
cplager+ucla@fnal.gov
Tue Feb 3 17:27:00 GMT 2004
Summary:
Emacs since being update has two common failure modes:
1) Taking all the CPU
2) Crashing.
An update:
* Updated cygwin to official 1.5.7-1 release
* As suggested, I have been trying to use strace -p on the emacs pid.
After updating strace from a snapshot, I was still having problems.
When emacs has gone into a mode that uses all the CPU, nothing shows up
on the strace output until I kill it (using kill.exe) and then I get the
output of the first attached file.
* One time emacs crashed, it left a stackdump file (second file attached)
* Third attachment is latest cygcheck.out (not much should have changed,
but just for completeness).
Thanks,
Charles
> * From: "I-Taylor, Trevor" <trevor dot taylor2 at boeing dot com>
> * To: <cygwin at cygwin dot com>
> * Date: Tue, 3 Feb 2004 09:20:23 +1000
> * Subject: re: Problems with Emacs
>
>>Yesterday, I reinstalled cygwin from scratch choosing (among other
>>packages) the latest version 21.2.12 of emacs. Most of the time I try to
>>start the program (using X) , it launches o.k. But sometimes, the window
>>pops up and it freezes taking all of the cpu (it says "loading ed mode").
>>I have repeatedly tried to uninstall and reinstall emacs and I keep
>>getting the same errors.
>>
>>Does anybody have any ideas? Has anybody else seen this?
>
> Yes,
>
> I updated my cygwin installation on friday 23 january 2004, and immediately emacs has become unreliable. Attached updated.txt shows what was updated.
>
> emacs core dumps regularly, sometimes when I'm not touching it, sometimes when I am. I tried to use dumper.exe to actually get a core dump. It didn't work the first couple of times (see attached "core dump from dumper"), but then I got a core dump with stack trace (seen twice):
>
> #0 0x77f83786 in ntdll!ZwWaitForSingleObject ()
> (gdb) bt
> #0 0x77f83786 in ntdll!ZwWaitForSingleObject ()
> #1 0x77e8780f in WaitForSingleObjectEx ()
> #2 0x77e87837 in WaitForSingleObject ()
> #3 0x000000c8 in ?? ()
> #4 0x0000ea60 in ?? ()
>
> I also got:
>
> - [3]+ Segmentation fault emacs (wd: /cygdrive/h/matrix-drawing-analysis-tools/lib)
>
> with no core dump (dumper didn't seem to be invoked) regularly
>
> - X protocol errors:
>
> this seems to have stopped happening, and I didn't capture
> the message at the times, but from memory it was something about
> a bad length. I tries running emacs "synchronous" under gdb
> to catch the stack trace at the time but gdb couldn't break in
> _XError (or main for that matter).
>
> I also tried:
>
> - running emacs -nw (didn't crash)
> - going back to XWin windowed mode (i.e. default behaviour), which is what I was using before any upgrades:
> - got emacs exit with Segmentation Fault (no core dump)
> - running emacs -q (still in XWin windowed mode):
> - got "Exit 128 emacs -q (wd: ~)" (no core dump)
> - building emacs from sources (the gnu emacs distribution):
> - configure doesn't know about cygwin
>
> How is the emacs code (officially) compiled for cygwin (it might help if I could compile it with debug and run it under gdb)?
>
> Trevor
--
------------------------------------------------------------------
Charles Plager cplager+ucla@fnal.gov
Dept of Physics, UCLA http://www-cdf.fnal.gov/~cplager
office: (1) 630-840-2575 fax: (1) 630-840-2968
------------------------------------------------------------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: emacs.strace
URL: <http://cygwin.com/pipermail/cygwin/attachments/20040203/bb66c620/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: emacs.exe.stackdump
URL: <http://cygwin.com/pipermail/cygwin/attachments/20040203/bb66c620/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck.out
URL: <http://cygwin.com/pipermail/cygwin/attachments/20040203/bb66c620/attachment-0002.ksh>
-------------- next part --------------
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list