Package: msn-pecan
Version: 0.0.18-1
Severity: important

I've not been able to find the exact cause for this issue to happen but every 
now and then pidgin would just crash. I 
installed pidgin-dbg and got the following backtrace:

(gdb) handle SIGPIPE noprint nostop
Signal        Stop      Print   Pass to program Description
SIGPIPE       No        No      Yes             Broken pipe
(gdb) run
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f5b750 (LWP 3820)]
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6f5b750 (LWP 3820)]
0xb776340e in g_hash_table_destroy () from /usr/lib/libglib-2.0.so.0
(gdb) bt
#0  0xb776340e in g_hash_table_destroy () from /usr/lib/libglib-2.0.so.0
#1  0xb55abdd8 in msn_message_destroy () from /usr/lib/purple-2/libmsn-pecan.so
#2  0xb55abeb6 in msn_message_unref () from /usr/lib/purple-2/libmsn-pecan.so
#3  0xb55abdc8 in msn_message_destroy () from /usr/lib/purple-2/libmsn-pecan.so
#4  0xb559b06b in ?? () from /usr/lib/purple-2/libmsn-pecan.so
#5  0x0a06f040 in ?? ()
#6  0x0a06f040 in ?? ()
#7  0x00000000 in ?? ()

I'll see about installing debug symbols for this package too and update this

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (100, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages msn-pecan depends on:
ii  libc6                         2.9-4      GNU C Library: Shared libraries
ii  libglib2.0-0                  2.20.0-2   The GLib library of C routines
ii  libpurple0                    2.5.5-1    multi-protocol instant messaging l

msn-pecan recommends no packages.

msn-pecan suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to