Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.23.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1553549
Title:
Mir crashes with useless backtrace when mg::Platform methods throw
Status in Mir:
Fix Committed
Status in Unity System Compositor:
Invalid
Status in mir package in Ubuntu:
Triaged
Status in unity-system-compositor package in Ubuntu:
Invalid
Bug description:
So, the problem that causes unity-system-compositor to crash (rather
than fail to start with a helpful error message) is that when methods
on mg::Platform throw we unload the platform DSO before exception
processing is completed, so libstdc++ goes merrily along trying to
execute code that is longer mapped.
Original report below:
unity-system-co[5574]: segfault at 7f8056ee2490 ip 00007f805c592c3b sp
00007fffd6b871a0 error 4 in libstdc++.so.6.0.21[7f805c506000+172000]
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 5 19:03:39 2016
ExecutablePath: /usr/sbin/unity-system-compositor
ExecutableTimestamp: 1455894356
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor
Integrated Graphics Controller [1462:1102]
Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX
970M] [1462:1102]
InstallationDate: Installed on 2015-02-25 (374 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/sbin/unity-system-compositor
--disable-inactivity-policy=true --on-fatal-error-abort --file
/run/lightdm-mir-0 --from-dm-fd 11 --to-dm-fd 20 --vt 8
ProcCwd: /
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0x7f805c592c3b: mov (%rsi),%rax
PC (0x7f805c592c3b) ok
source "(%rsi)" (0x7f8056ee2490) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-system-compositor
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
__gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
_Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
_Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
__cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
UpgradeStatus: Upgraded to xenial on 2015-11-03 (122 days ago)
UserGroups:
version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.17.5-0ubuntu2
version.mesa: libegl1-mesa-dev N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1553549/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
