[OpenIndiana-discuss] mate-system-monitor crashes

Wed Feb 8 10:31:36 UTC 2023

On 08/02/2023 07:02, Stephan Althaus wrote:
> On 2/7/23 22:29, Stephan Althaus wrote:
>> On 2/7/23 22:11, Bill Sommerfeld wrote:
>>> On 2/7/23 13:01, Matthew Yapit wrote:
>>>> I recently updated to 2022.10 and I've noticed that mate-system-monitor
>>>> causes a core instead of launching.  Has anyone else seen this?  Is there a
>>>> fix or one coming in the next update?
>>>
>>> It happens for me, too.   Based on the traceback in exception code, it likely
>>> needs to be rebuilt with gcc 10 given the lack of C++ ABI stability.   ldd
>>> shows a mix of libraries:
>>>
>>> % ldd =mate-system-monitor  | grep gcc
>>>         libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
>>>         libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
>>>         libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
>>>         libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
>>>
>>>
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> Hello!
>>
>> My version of mate-system-monitor shows only the gcc 7 libs,
>> but maybe you're right anyway..
>>
>>
>> $ ldd `which mate-system-monitor`  | grep gcc
>>         libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
>>         libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
>>
>> $ mate-system-monitor
>>
>> ...
>>
>> (<unknown>:4743): glibmm-CRITICAL **: 22:24:52.725:
>> unhandled exception (type Glib::Error) in signal handler:
>> domain: g-io-error-quark
>> code  : 0
>> what  : Unable to find default local file monitor type
>>
>> Segmentation Fault (core dumped)
>>
>> $ pstack core
>> core 'core' of 4743:    mate-system-monitor
>> --------------------- thread# 1 / lwp# 1 ---------------------
>>  00007fffaeb69d0b g_type_check_instance_cast () + 1b
>>  000000000044977a
>> _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE
>> () + 11a
>>  00007fff6e3c09b9
>> _ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine
>> () + 149
>>  00007fffae841496 _g_cclosure_marshal_INT__OBJECTv () + 76
>>  00007fffaeb3af95 _g_closure_invoke_va () + 185
>>  00007fffaeb5af6d g_signal_emit_valist () + 39d
>>  00007fffaeb5c05d g_signal_emit () + 7d
>>  00007fffae8a032a g_application_call_command_line () + 7a
>>  00007fffae8a26b1 g_application_real_local_command_line () + 241
>>  00007fff6e3bf4f4 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 54
>>  00007fff6e3c05cb
>> _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi
>> () + 10b
>>  00007fffae8a2845 g_application_run () + 155
>>  0000000000422b4e main () + 5e
>>  0000000000421e07 _start_crt () + 87
>>  0000000000421d68 _start () + 18
>> ...
>>
>
>
> When i rebuild mate-system-monitor in my environment,
> i will get the dependencies to gcc-10 in the build.
>
> The pstack of the core then contains on entry "????????" which i assume is a
> result of the gcc-10 dependencies.
>
> Nevertheless mate-system-monitor does crash in the version (as of my BE:
> openindiana-2022:11:23) without gcc-10 deps.
>
> So the primary root cause may be something different.

It's the same crash in the current version. The gcc 7/10 mix results
from other libraries linked, see

# ldd -v `which mate-system-monitor`

With dbx, I get this stack:

(dbx) where -h -l -v
current thread: t at 1
=>[1] libc.so.1:_lwp_kill(0x1, 0x6, 0xfffffe116fe54400, 0x0, 0x0, 
0x5fffaeef2cf0), at 0x5fffaed8731a
   [2] libc.so.1:thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaed7dbe0
   [3] libc.so.1:raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaed1b26e
   [4] libc.so.1:abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaecf4cd8
   [5] libgcc_s.so.1:_Unwind_SetGR(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaff52b0e
   [6] libstdc++.so.6.0.24:__gxx_personality_v0(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), 
at 0x5fffaeff08c1
   [7] 0x7fffbffde8a0(0x0), at 0x7fffbffde8a0
   [8] libgcc_s.so.1:_Unwind_RaiseException_Phase2(0x0), at 0x5fffae705756
   [9] libgcc_s.so.1:_Unwind_Resume(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 
0x5fffae706126
   [10] 
libgiomm-2.4.so.1.3.0:_ZN3Gio4File17monitor_directoryENS_16FileMonitorFlagsE.cold(0x0, 
0x0, 0x0, 0x0, 0x0, 0x0), at 0x5fffaeb9b9d5
   [11] mate-system-monitor:PrettyTable::PrettyTable(0x0, 0x0, 0x0, 0x0, 0x0, 
0x0), at 0x42f84b
   [12] mate-system-monitor:ProcData::get_instance(0x0, 0x0, 0x0, 0x0, 0x0, 
0x0), at 0x4223e1

or, in mdb (on parent)
 > ::stack
libc.so.1`_lwp_kill+0xa()
libc.so.1`raise+0x1e(6)
libc.so.1`abort+0x58()
0x5fffaffb2b0e()
libstdc++.so.6.0.24`__gxx_personality_v0+0xd1()
libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
libgcc_s.so.1`_Unwind_Resume+0x126()
0x5fffae39b9d5()
_ZN11PrettyTableC1Ev+0x1db()
_ZN8ProcData12get_instanceEv+0x81()
_ZL16procman_data_newP10_GSettings+0x1c()
_ZN10ProcmanApp10on_startupEv+0x4d()
libgiomm-2.4.so.1.3.0`_ZN3Gio17Application_Class16startup_callbackEP13_GApplication+0xc5()
libgobject-2.0.so.0.7400.5`_g_closure_invoke_va+0x188()
libgobject-2.0.so.0.7400.5`g_signal_emit_valist+0xd59()
libgobject-2.0.so.0.7400.5`g_signal_emit+0x7d()
libgio-2.0.so.0.7400.5`g_application_register+0x122()
libgio-2.0.so.0.7400.5`g_application_real_local_command_line+0x6a()
libgiomm-2.4.so.1.3.0`_ZN3Gio11Application24local_command_line_vfuncERPPcRi+0x52()
libgiomm-2.4.so.1.3.0`_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi+0xfb()
libgio-2.0.so.0.7400.5`g_application_run+0x133()
main+0x5e()
_start_crt+0x87()
_start+0x18()

-- 
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology           http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026