Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: emacs component: emacs crash_function: hash_lookup executable: /usr/bin/emacs-23.2 kernel: 2.6.35.10-74.fc14.x86_64 package: emacs-1:23.2-7.fc14 rating: 3 reason: Process /usr/bin/emacs-23.2 was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1294987759 uid: 500 comment ----- emacs ran better on Multics and TOPS-20 than it does on Fedora. This is not the only bad emacs bug. In practice it's barely usable with its weird behavior. What is going on? I have never before seen a "released" platform where emacs runs so poorly. How to reproduce ----- 1. this is a vmware fusion vm, the files are on a gvfs partition 2. edit java source files for hours 3. run M-x compile to build java programs, and esc-` to parse error messages 4. try running java programs in gnome-terminal shell window, to see if they work 5. edit more source code 6. lather rinse repeat until... 7. boom! random crash out of nowhere
Created attachment 473477 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 667884 ***