emacs crashes with "illegal instruction" on first RET in empty file

Bug #685031 reported by Andrew Tinka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emacs-snapshot (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: emacs-snapshot

Steps to reproduce:

1. touch blah.txt
2. emacs blah.txt
3. RET

Result: emacs crashes; terminal says "illegal instruction".

Some notes:
* emacs had been working just fine on this machine for many months. I don't know what changed.
* Reproduceability is 100%.
* There are many customizations in my ~/.emacs.d directory; however, I can elicit this behaviour both with my normal configuration and after deleting ~/.emacs.d . In other words, it isn't my customizations that are doing this.
* There are many other input sequences that cause this behaviour. For example, if editing a Python file, Ctrl-C Ctrl-C (to run the file in the interactive Python window) causes the crash. However, I haven't tested this in the "no-.emacs.d" state, and the above sequence is the *simplest* way I've found to cause the crash.

ProblemType: Bug
Architecture: amd64
Date: Fri Dec 3 16:27:08 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/emacs-snapshot-gtk
NonfreeKernelModules: nvidia
Package: emacs-snapshot 1:20090909-1
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-22.68-generic
SourcePackage: emacs-snapshot
Uname: Linux 2.6.31-22-generic x86_64

Revision history for this message
Andrew Tinka (tinka-berkeley) wrote :
Revision history for this message
Andrew Tinka (tinka-berkeley) wrote :

Well, I rebooted the machine, and now the bug doesn't occur. Weird. I guess this isn't "100% reproduceable" anymore.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.