[apport] emacs-snapshot-gtk crashed with SIGSEGV in __kernel_vsyscall()

Bug #115242 reported by CTW
2
Affects Status Importance Assigned to Milestone
emacs-snapshot (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: emacs-snapshot

This is almost certainly a duplicate. Emacs-snapshot crashes when I try to open it by double-clicking on a text file that's associated with it. If I explicitly open it and then manually load the file, it works.

ProblemType: Crash
Architecture: i386
Date: Thu May 17 10:28:18 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/emacs-snapshot-gtk
Package: emacs-snapshot-gtk 1:20061218-1
PackageArchitecture: i386
ProcCmdline: /usr/bin/emacs-snapshot-gtk /home/ctw/src/pyeeg/src/data.py
ProcCwd: /home/ctw
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: emacs-snapshot
StacktraceTop:
 __kernel_vsyscall ()
 kill () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Uname: Linux kahamac1 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
CTW (ctw) wrote :
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. I don't have this problem with Xubuntu 7.04, I will try with Ubuntu and see if I can confirm this bug.

Changed in emacs-snapshot:
assignee: nobody → jerome-guelfucci
status: Unconfirmed → Needs Info
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__kernel_vsyscall ()
kill () from /lib/tls/i686/cmov/libc.so.6
fatal_error_signal (sig=11) at emacs.c:397

strcmp () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

I couldn't reproduce this on Ubuntu Feisty, I'm living this as unconfirmed.

Changed in emacs-snapshot:
assignee: jerome-guelfucci → nobody
importance: Undecided → Low
status: Needs Info → Unconfirmed
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Do you still have this issue ?

Changed in emacs-snapshot:
status: New → Incomplete
Revision history for this message
CTW (ctw) wrote :

On one of my machines the issue seems to be gone. On my other machine th issue remains. I'm not sure why it got fixed on one of my machine and not on the other. They are both 32 bit Feisty installations and I keep both up to date.

Here's what happens when I try to run it:
$ emacs-snapshot-gtk
Fatal error (11)Segmentation fault (core dumped)

Revision history for this message
CTW (ctw) wrote :

I should clarify: I have narrowed the issue down to emacs-snapshot-gtk. emacs-snapshot-x works fine on both machines.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Can you test with a newer version of emacs-snapshot-gtk ?

Maybe from here (in your sources.list)

deb http://ppa.launchpad.net/avassalotti/ubuntu feisty main

Please note that these are not official Ubuntu packages !

Revision history for this message
CTW (ctw) wrote : Re: [Bug 115242] Re: [apport] emacs-snapshot-gtk crashed with SIGSEGV in

On 9/18/07, Jérôme Guelfucci - <email address hidden> wrote:
> Can you test with a newer version of emacs-snapshot-gtk ?
>
> Maybe from here (in your sources.list)
>
> deb http://ppa.launchpad.net/avassalotti/ubuntu feisty main
>
> Please note that these are not official Ubuntu packages !

This version works fine.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok so it means it has been fixed in the new releases of emacs-snapshot (in Gutsy for example). I'm marking this as fixed.

Changed in emacs-snapshot:
status: Incomplete → Fix Released
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.