Binary package hint: nano
Steps to reproduce:
1) Put some content into a file, e.g. echo f >f
2) open nano without arguments, or with a filename argument different from the above
3) ^O to save your work into the file 'f' (if you started nano with no arguments, you can also trigger the bug via ^X)
4) Watch nano segfault.
This happens every time. Since nano is the default editor, this is critical. I don't know how other people use nano but I like to be able to save important work with a different filename, and a segfault is unacceptable here.
ProblemType: Crash
Architecture: amd64
Date: Mon Nov 2 14:48:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /bin/nano
Package: nano 2.0.9-2
ProcCmdline: nano
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
Segfault happened at: 0x40900a: cmp %rcx,0x58(%rax)
PC (0x0040900a) ok
source "%rcx" ok
destination "0x58(%rax)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nano
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: nano crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
Probably not relevant, but just in case it is, this is on a machine that was upgraded from jaunty via apt-get dist-upgrade.