[orca-list] Fwd: Re: crashes of MATE .18 apps clicking on About if orca is running

[Didier Spaier <didier slint fr>]

I forgot to send this message also to the list, sorry.

Didier


-------- Message transféré --------
Sujet : Re: [orca-list] crashes of MATE .18 apps clicking on About if orca is running
Date : Wed, 13 Dec 2017 18:30:13 +0100
De : Didier Spaier
Pour : Alex ARNAUD



Le 13/12/2017 à 18:17, Alex ARNAUD a écrit :
> Le 13/12/2017 à 18:11, Didier Spaier a écrit :
> > I m not accustomed to using GDB.
> >
> > Could you please suggest which arguments and options would be relevant?
>
> I'm not a GDB expert myself.
>
> The commands could be:
> 1) gdb pluma
> 2) On the gdb prompt type "run" to launch pluma
> 3) Do the steps to produce the crash
> 4) Check the backtrace with the command: bt or bt full

Thanks.
Here are the results.
cut here
(gdb) run
Starting program: /usr/bin/pluma 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffebd92700 (LWP 6735)]
[New Thread 0x7fffeb591700 (LWP 6736)]
[New Thread 0x7fffe9493700 (LWP 6737)]

Thread 1 "pluma" received signal SIGSEGV, Segmentation fault.
0x00007ffff6b17395 in ?? () from /usr/lib64/../lib64/libgtk-3.so.0
(gdb) bt
#0  0x00007ffff6b17395 in  () at /usr/lib64/../lib64/libgtk-3.so.0
#1  0x00007fffed9f63ba in emit_event () at /usr/lib64/../lib64/libatk-bridge-2.0.so.0
#2  0x00007fffed9f74a1 in property_event_listener () at /usr/lib64/../lib64/libatk-bridge-2.0.so.0
#3  0x00007fffef48ce9b in  () at /usr/lib64/../lib64/libgobject-2.0.so.0
#4  0x00007fffef495d6f in g_signal_emit_valist () at /usr/lib64/../lib64/libgobject-2.0.so.0
#5  0x00007fffef496092 in g_signal_emit () at /usr/lib64/../lib64/libgobject-2.0.so.0
#6  0x00007ffff5d5c152 in  () at /usr/lib64/../lib64/libatk-1.0.so.0
#7  0x00007fffef47b935 in g_closure_invoke () at /usr/lib64/../lib64/libgobject-2.0.so.0
#8  0x00007fffef48cc7c in  () at /usr/lib64/../lib64/libgobject-2.0.so.0
#9  0x00007fffef495d6f in g_signal_emit_valist () at /usr/lib64/../lib64/libgobject-2.0.so.0
#10 0x00007fffef496092 in g_signal_emit () at /usr/lib64/../lib64/libgobject-2.0.so.0
#11 0x00007fffef47fb24 in  () at /usr/lib64/../lib64/libgobject-2.0.so.0
#12 0x00007fffef481ed3 in g_object_notify () at /usr/lib64/../lib64/libgobject-2.0.so.0
#13 0x00007ffff6b1872f in  () at /usr/lib64/../lib64/libgtk-3.so.0
#14 0x00007ffff6b187af in  () at /usr/lib64/../lib64/libgtk-3.so.0
#15 0x00007ffff6dc10a7 in  () at /usr/lib64/../lib64/libgtk-3.so.0
#16 0x00007ffff6b11394 in  () at /usr/lib64/../lib64/libgtk-3.so.0
#17 0x00007fffed9f1ac3 in add_pending_items () at /usr/lib64/../lib64/libatk-bridge-2.0.so.0
#18 0x00007fffeef7564a in g_main_context_dispatch () at /usr/lib64/../lib64/libglib-2.0.so.0
#19 0x00007fffeef759c8 in  () at /usr/lib64/../lib64/libglib-2.0.so.0
#20 0x00007fffeef75ce2 in g_main_loop_run () at /usr/lib64/../lib64/libglib-2.0.so.0
#21 0x00007ffff6c8c985 in gtk_main () at /usr/lib64/../lib64/libgtk-3.so.0
#22 0x000000000042837d in main ()
cut here.

It seems that gtk3 be involved, now what?

Best regards,

Didier