sakura crashed with SIGSEGV in _start()

Bug #939754 reported by Daniel Richard G. on 2012-02-23
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sakura (Ubuntu)
Medium
Unassigned

Bug Description

Closed sakura, got a segfault.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: sakura 2.4.2-1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Feb 23 14:25:15 2012
ExecutablePath: /usr/bin/sakura
ProcCmdline: sakura
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LC_COLLATE=C
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x40a087 <_start+9119>: mov 0x8(%rax),%r13
 PC (0x0040a087) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: sakura
Stacktrace:
 #0 0x000000000040a087 in _start ()
 No symbol table info available.
StacktraceTop: _start ()
Title: sakura crashed with SIGSEGV in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout floppy plugdev scanner vboxusers video

Revision history for this message
Daniel Richard G. (skunk) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x000000000040a087 in _start ()
 No symbol table info available.
StacktraceTop: _start ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in sakura (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers