emacs23-x crashed with SIGSEGV

Bug #795197 reported by Jae-hyeon Park
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
emacs23 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: emacs23

Emacs crashed while I was not using it and a window popped up asking me to report the problem.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: emacs23 23.2+1-7ubuntu2
Uname: Linux 2.6.39-1-tuxonice x86_64
Architecture: amd64
Date: Thu Jun 9 20:03:56 2011
ExecutablePath: /usr/bin/emacs23-x
ProcCmdline: /usr/bin/emacs
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x567e2a: mov 0x10(%rcx,%rdx,8),%rbp
 PC (0x00567e2a) ok
 source "0x10(%rcx,%rdx,8)" (0x025da790) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: emacs23
Stacktrace:
 #0 0x0000000000567e2a in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffffd4df5d8
StacktraceTop: ?? ()
Title: emacs23-x crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-06-08 (1 days ago)
UserGroups: adm admin audio cdrom dialout kvm lpadmin plugdev pulse-access sambashare
XsessionErrors: (gnome-terminal:3208): Gtk-CRITICAL **: IA__gtk_paint_extension: assertion `style->depth == gdk_drawable_get_depth (window)' failed

Revision history for this message
Jae-hyeon Park (jhyeon) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x0000000000567e2a in hash_lookup (h=0xb44c70, key=11819570, hash=0x0) at fns.c:4129
         hash_code = 2954894
         idx = <value optimized out>
 Cannot access memory at address 0x7ffffd4df5d8
StacktraceTop: hash_lookup (h=0xb44c70, key=11819570, hash=0x0) at fns.c:4129

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in emacs23 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
RedSingularity (redsingularity) wrote :

Since this report does not contain any personal information, I am marking it public.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

visibility: private → public
Revision history for this message
Roland Dreier (roland.dreier) wrote :

I've started getting emacs crashes pretty often today after the latest set of Oneiric updates. Yesterday emacs was completely stable, so it's something in the last 24 hours or so.

Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in emacs23 (Ubuntu):
status: New → Invalid
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.