virtuoso-t crashed with SIGSEGV in dk_free_tree()

Bug #981159 reported by Balaam's Miracle
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
virtuoso-opensource (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: virtuoso-opensource-6.1-bin 6.1.4+dfsg1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Apr 13 13:45:16 2012
ExecutablePath: /usr/bin/virtuoso-t
ProcCmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_qq3722.ini +wait
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8463bda <dk_free_tree+42>: movzbl -0x1(%edi),%edx
 PC (0x08463bda) ok
 source "-0x1(%edi)" (0xfeedb9ff) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtuoso-opensource
StacktraceTop:
 dk_free_tree ()
 dk_free_tree ()
 dk_free_tree ()
 ?? ()
 ?? ()
Title: virtuoso-t crashed with SIGSEGV in dk_free_tree()
UpgradeStatus: Upgraded to precise on 2012-03-05 (39 days ago)
UserGroups: adm admin audio avahi cdrom dialout dip floppy fuse games lpadmin netdev plugdev powerdev pulse sambashare scanner users video

Revision history for this message
Balaam's Miracle (balaam-balaamsmiracle) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in virtuoso-opensource (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in virtuoso-opensource (Ubuntu):
status: New → Confirmed
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.