ardour-2.8.12 crashed with SIGSEGV in g_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ardour (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Automatic bug report
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ardour 1:2.8.12-1
ProcVersionSign
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/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/
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_
g_mutex_lock () from /lib/x86_
Lock (mutex=..., this=<synthetic pointer>) at /usr/include/
ARDOUR:
AutomationLine
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
Changed in ardour (Ubuntu): | |
status: | New → Fix Released |