foo-yc20 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

Bug #1037397 reported by Blair Chasteen on 2012-08-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
foo-yc20 (Ubuntu)

Bug Description

Ubuntu Studio Live Quantal a3. Attempt to launch via menu top left my dvd-ram drive spun up and nothing appeared until crash report.
Linux ubuntu-studio 3.5.0-9-lowlatency #8-Ubuntu SMP PREEMPT Thu Aug 9 16:53:37 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: foo-yc20 1.3.0-5
ProcVersionSignature: Ubuntu 3.5.0-9.8-lowlatency 3.5.0
Uname: Linux 3.5.0-9-lowlatency x86_64
ApportVersion: 2.4-0ubuntu7
Architecture: amd64
CasperVersion: 1.320
Date: Thu Aug 16 04:18:02 2012
ExecutablePath: /usr/bin/foo-yc20
LiveMediaBuild: Ubuntu-Studio 12.10 "Quantal Quetzal" - Alpha amd64 (20120813)
ProcCmdline: foo-yc20
 PATH=(custom, no user)
Signal: 6
SourcePackage: foo-yc20
 raise () from /lib/x86_64-linux-gnu/
 abort () from /lib/x86_64-linux-gnu/
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 std::terminate() () from /usr/lib/x86_64-linux-gnu/
Title: foo-yc20 crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Blair Chasteen (darkstormyrain) wrote :
visibility: private → public

 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/
 __cxxabiv1::__cxa_throw (obj=0x1c3d1e0, tinfo=<optimized out>, dest=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/
 ?? ()

Changed in foo-yc20 (Ubuntu):
importance: Undecided → Medium
summary: - foo-yc20 crashed with SIGABRT in raise()
+ foo-yc20 crashed with SIGABRT in
+ __gnu_cxx::__verbose_terminate_handler()
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers