virtuoso-t crashed with SIGSEGV

Bug #1283597 reported by Phil Wyett on 2014-02-23
66
This bug affects 14 people
Affects Status Importance Assigned to Milestone
virtuoso-opensource (Ubuntu)
High
Unassigned

Bug Description

Random crash. Will look to get data and report upstream.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: virtuoso-opensource-6.1-bin 6.1.6+repack-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Feb 23 00:12:08 2014
ExecutablePath: /usr/bin/virtuoso-t
InstallationDate: Installed on 2014-02-20 (2 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140220)
ProcCmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_ik2226.ini +wait
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x939d75: movq $0xffffffffffffffff,(%rax)
 PC (0x00939d75) ok
 source "$0xffffffffffffffff" ok
 destination "(%rax)" (0xffffffffffffffff) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: virtuoso-opensource
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: virtuoso-t crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Phil Wyett (aura-yoda) wrote :
information type: Private → Public

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtuoso-opensource (Ubuntu):
status: New → Confirmed

It prevents the package (or a dependent one) from functioning correctly at all.

Changed in virtuoso-opensource (Ubuntu):
importance: Undecided → High
cornelis stravers (cd-stravers) wrote :

happened while running "synaptic" update on an up to date 14.04 on a Toshiba Satellite C55a

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

Other bug subscribers