29 Nov 2006 22:24
Emacs hangs upon loading cedet
Stephen Berman <Stephen.Berman <at> gmx.net>
2006-11-29 21:24:13 GMT
2006-11-29 21:24:13 GMT
I'm using current CVS cedet with the first Emacs 22 pretest tarball (GNU Emacs 22.0.90.1 (i686-pc-linux-gnu, GTK+ Version 2.8.10) of 2006-11-07 on escher). I've run across a file[1] that causes Emacs to hang or loop infinitely when I try to visit it after loading cedet. There are two cases (both with emacs -Q): (i) Do M-: (load-file "<path to>/cedet/common/cedet.el") and then visit the file. The file gets loaded into a buffer but then Emacs immediately goes into a loop and consumes 100% CPU. The loop can be broken by C-g. (ii) Do M-: (load-file "<path to>/cedet/common/cedet.el"), then M-: (semantic-load-enable-code-helpers) and then visit the file. Emacs immediately hangs, consuming 100% CPU, without the file being visible in a buffer. C-g has no effect in this case, only kill -9. I reproduced case (ii) under gdb and got the following lisp backtrace: "byte-code" (0x8a51b73) "byte-code" (0x8a51ba3) "semantic-parse-stream-default" (0x8dfa3b5) "semantic-parse-stream" (0x8dfa3b5) "semantic-repeat-parse-whole-stream" (0x836da7d) "semantic-parse-region-default" (0x8) "semantic-parse-region" (0x8) "semantic-fetch-tags" (0x0) "semantic-create-imenu-index" (0x84c6101) "imenu--make-index-alist" (0x83168f9) "imenu-update-menubar" (0x82ce304) "run-hooks" (0x8343631) (I assume the problem is somewhere is the cedet or semantic lisp, but maybe it's in the byte-code produced. I can provide the C backtrace if desired, which shows numerous calls to Fbyte_code.)(Continue reading)
RSS Feed