I have this bug too with the same versione of piding (2.7.1-1), random
crashes when I'm not even using the program.
I'm attaching a backtrace I took following the instruction on the
pidgin's site (http://developer.pidgin.im/wiki/GetABacktrace), hope it
helps.
Don't know if related but this bug came out just a few days ago when i
stopped using msn-pecan plugin for my msn account and went back to the
default pidgin's msn protocol, I can switch back to msn-pecan and see if
it will still crash if you think it could help.
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f
Sponsor:
Jeans uomo e donna a Euro 14,99 li trovi solo su piazzaitalia.it, guarda tutta
la collezione
*
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=10490&d=8-6
GNU gdb (GDB) 7.1-debian
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pidgin...(no debugging symbols found)...done.
(gdb) handle SIGPIPE nostop noprint
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]
Program received signal SIGINT, Interrupt.
0x00007ffff4a710e8 in poll () from /lib/libc.so.6
(gdb) quit
A debugging session is active.
Inferior 1 [process 30707] will be killed.
Quit anyway? (y or n)
