On Sat, Jan 24, 2009 at 03:41:11PM -0500, Ari Pollak wrote:
> Could you attach a backtrace of the crash?
Sure. Backlog from pidgin 2.5.3-1:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6ffb730 (LWP 27721)]
msn_soap_read_cb (data=0xb362f60, fd=24, cond=PURPLE_INPUT_READ)
at ../../../../libpurple/protocols/msn/soap.c:345
345 ../../../../libpurple/protocols/msn/soap.c: No such file or
directory.
in ../../../../libpurple/protocols/msn/soap.c
(gdb) bt
#0 msn_soap_read_cb (data=0xb362f60, fd=24, cond=PURPLE_INPUT_READ)
at ../../../../libpurple/protocols/msn/soap.c:345
#1 0x080a8763 in pidgin_io_invoke (source=0xb3a41f0,
condition=<value optimized out>, data=0xb375b00)
at ../../pidgin/gtkeventloop.c:78
#2 0xb7738eed in g_io_unix_dispatch (source=0xb35b478,
callback=0x80a8720 <pidgin_io_invoke>, user_data=0xb375b00)
at /build/buildd/glib2.0-2.18.4/glib/giounix.c:162
#3 0xb7702398 in IA__g_main_context_dispatch (context=0xa0a8220)
at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2144
#4 0xb7705a33 in g_main_context_iterate (context=0xa0a8220, block=1,
dispatch=1, self=0xa0833e8)
at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2778
#5 0xb7705f52 in IA__g_main_loop_run (loop=0xaf34fa0)
at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2986
#6 0xb7aff2b9 in IA__gtk_main ()
at /build/buildd/gtk+2.0-2.14.7/gtk/gtkmain.c:1200
#7 0x080c2836 in main (argc=0, argv=0x0) at ../../pidgin/gtkmain.c:884
I also managed to track down an upstream report about this, which
also contains a backtrace:
http://developer.pidgin.im/ticket/7508
Dunno if it's any help though.
Regards: David
--
/) David Weinehall <t...@debian.org> /) Rime on my window (\
// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/ (/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
