ardour-2.8.12 crashed with SIGSEGV in g_mutex_lock()

Bug #926697 reported by Trond Aasan on 2012-02-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ardour (Ubuntu)
Undecided
Unassigned

Bug Description

Automatic bug report

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ardour 1:2.8.12-1
ProcVersionSignature: Ubuntu 3.2.0-13.22~ppa1-lowlatency 3.2.2
Uname: Linux 3.2.0-13-lowlatency x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 4 15:35:17 2012
ExecutablePath: /usr/lib/ardour2/ardour-2.8.12
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/ardour2/ardour-2.8.12
SegvAnalysis:
 Segfault happened at: 0x7fd15cf8fe46: mov (%rdi),%r12
 PC (0x7fd15cf8fe46) ok
 source "(%rdi)" (0x00000041) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ardour
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 Lock (mutex=..., this=<synthetic pointer>) at /usr/include/glibmm-2.4/glibmm/thread.h:806
 ARDOUR::AutomationList::apply_to_points<AutomationLine> (this=0x69394e8, obj=..., method=(void (AutomationLine::*)(AutomationLine * const, const ARDOUR::AutomationList &)) 0x5ad540 <AutomationLine::reset_callback(ARDOUR::AutomationList const&)>) at libs/ardour/ardour/automation_event.h:163
 AutomationLine::reset (this=<optimized out>) at gtk2_ardour/automation_line.cc:1245
Title: ardour-2.8.12 crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip floppy fuse lpadmin plugdev sambashare sudo

Trond Aasan (trond-aasan) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers