Re: [orca-list] pidgin crashing randomly when restarting orca



Hi,
I guess I'm stuck. Using that command didn't help at all, gdb is now complaining there are no symbole tables so it only prit question marks. Guess I'll have to go and run pidgin in gdb...

Le 2016-10-24 13:25, Joanmarie Diggs a écrit :
Try:

1. gdb --core <existing core dump file name>
2. bt full

--joanie

On 10/24/2016 12:45 PM, Tyna Pelletier-Bilodeau wrote:
Hi again,
at the risk of sounding dumb *grins*, how can I get a full backtrace ?
Do I need to run pidgin in gdb and wait till the crash happens ? Cause
this crash is really hard to reproduce, sometimes it will happen,
sometimes not. If I have to, I will, I just hoped this core dump could
be more useful than that
Thanks !

Le 2016-10-24 11:34, Joanmarie Diggs a écrit :
Could you get a full backtrace?
--joanie

On 10/24/2016 07:49 AM, Tyna Pelletier-Bilodeau wrote:
Hi,
since this is kinda hard to reproduce, I kept the full core dump and ran
gdb on it with: coredumpctl gdb 15857 -- the pid of pidgin at the time
of the crash. Then I used bt to get the backtrace, and here it is:

#0  0x00007ff063c9004f in raise () at /usr/lib/libc.so.6
#1  0x00007ff063c9147a in abort () at /usr/lib/libc.so.6
#2  0x000000000048125a in  ()
#3  0x00007ff06400c080 in <signal handler called> () at
/usr/lib/libpthread.so.0
#4  0x00007ff064ba483d in g_type_check_instance_is_fundamentally_a () at
/usr/lib/libgobject-2.0.so.0
#5  0x00007ff064b8488e in g_object_ref () at
/usr/lib/libgobject-2.0.so.0
#6  0x00007ff064896840 in g_hash_table_foreach () at
/usr/lib/libglib-2.0.so.0
#7  0x00007ff05876517d in  () at /usr/lib/libatk-bridge-2.0.so.0
#8  0x00007ff058762388 in  () at /usr/lib/libatk-bridge-2.0.so.0
#9  0x00007ff066f44993 in  () at /usr/lib/libdbus-1.so.3
#10 0x00007ff066f36014 in dbus_connection_dispatch () at
/usr/lib/libdbus-1.so.3
#11 0x00007ff05852f7b5 in  () at /usr/lib/libatspi.so.0
#12 0x00007ff0648a7587 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#13 0x00007ff0648a77f0 in  () at /usr/lib/libglib-2.0.so.0
#14 0x00007ff0648a7b12 in g_main_loop_run () at
/usr/lib/libglib-2.0.so.0
#15 0x00007ff065b6c3a7 in gtk_main () at /usr/lib/libgtk-x11-2.0.so.0
#16 0x0000000000431f59 in main ()

Oof sorry it was a bit spammy. Anyway, I hope this will help to know
what is actually going on. If it requires something else please let me
know, I will not delete the core dump until this issue has been either
fixed or reported to pidgin themselves.
Thanks !

Le 2016-10-24 05:50, Joanmarie Diggs a écrit :
Hi Tyna.

If Pidgin is segfaulting, it would be helpful if you could run pidgin
under gdb, trigger the crash, and then see where the crash is
occurring.

--joanie

On 10/20/2016 05:37 AM, Tyna Pelletier-Bilodeau wrote:
Hi all,
last week I noticed a strange bug with pidgin and orca that I didn't
notice before. Sometimes orca seems to hangs a bit, or it takes up
a lot
of memory so I need to restart it, but in doing so, it causes
pidgin to
crash rather badly, badly as in segfault. Is there a way to put that
full segfault somewhere so someone can examine it ? Should I simply
paste the thing with a pasting service ?
Thanks
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org

_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]