This is what happened when I ran the command:
fangfufu@illustrious:~$ pidgin -d pidgin.log
Pidgin 2.10.11 has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.
Thanks. One other thing - would you mind running pidgin -d
pidginlog.txt, reproducing the bug, and attaching the log file? You might
want to look through the file first to see if there's any personal
information that shouldn't be exposed.
There you go, the new backtrace:
Program received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x8006f) at malloc.c:2929
2929malloc.c: No such file or directory.
(gdb) bt
#0 __GI___libc_free (mem=0x8006f) at malloc.c:2929
#1 0x7558c86b in g_string_free ()
from
Would you mind sending a new backtrace after installing the pidgin-dbg
package?
Package: pidgin
Version: 2.10.11-1
Severity: important
Dear Maintainer,
I use Pidgin's IRC feature. Occasionally when the network disconnects, Pidgin
crashes. This bug can be easily reproduced by running Pidgin, signing in an IRC
account, and send the computer to sleep. Pidgin is guaranteed to
5 matches
Mail list logo
