Your message dated Sat, 18 Sep 2010 01:48:10 +0200
with message-id <[email protected]>
and subject line Re: pidgin: crash when trying to do a chat (MSN)
has caused the Debian Bug report #469477,
regarding pidgin segfaults when being invited into a (msn-)conference
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
469477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469477
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pidgin
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 1972
Maintainer: Ari Pollak <[email protected]>
Architecture: amd64
Version: 2.4.3-4
Pidgin segfaults everytime when I'm invited into a msn-conference.
==============================
$ pidgin
GtkVBox
GtkVBox
Pidgin 2.4.3 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.
If you can reproduce the crash, please notify the developers
by reporting a bug at:
http://developer.pidgin.im/simpleticket/
Please make sure to specify what you were doing at the time
and post the backtrace from the core file. If you do not know
how to get the backtrace, please read the instructions at
http://developer.pidgin.im/wiki/GetABacktrace
If you need further assistance, please IM either SeanEgn or
LSchiere (via AIM). Contact information for Sean and Luke
on other protocols is at
http://developer.pidgin.im/wiki/DeveloperPages
Aborted
$
==============================
The whole application crashes immediately.
I ran pidgin with valgrind to trace down the error a bit:
==============================
$ pidgin
==21656== Memcheck, a memory error detector.
==21656== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==21656== Using LibVEX rev 1854, a library for dynamic binary translation.
==21656== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==21656== Using valgrind-3.3.1-Debian, a dynamic binary instrumentation
framework.
==21656== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==21656== For more details, rerun with: -v
==21656==
==21669==
==21669== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1434 from 3)
==21669== malloc/free: in use at exit: 9,548,291 bytes in 85,570 blocks.
==21669== malloc/free: 345,445 allocs, 259,875 frees, 50,101,070 bytes
allocated.
==21669== For counts of detected errors, rerun with: -v
==21670==
==21670== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1434 from 3)
==21670== malloc/free: in use at exit: 9,549,722 bytes in 85,591 blocks.
==21670== malloc/free: 345,545 allocs, 259,954 frees, 50,105,234 bytes
allocated.
==21670== For counts of detected errors, rerun with: -v
==21669== searching for pointers to 85,570 not-freed blocks.
==21670== searching for pointers to 85,591 not-freed blocks.
==21670== checked 15,148,920 bytes.
==21670==
==21670== LEAK SUMMARY:
==21670== definitely lost: 262,049 bytes in 5,343 blocks.
==21670== possibly lost: 364,663 bytes in 301 blocks.
==21670== still reachable: 8,923,010 bytes in 79,947 blocks.
==21670== suppressed: 0 bytes in 0 blocks.
==21670== Rerun with --leak-check=full to see details of leaked memory.
==21669== checked 15,147,368 bytes.
==21669==
==21669== LEAK SUMMARY:
==21669== definitely lost: 262,049 bytes in 5,343 blocks.
==21669== possibly lost: 364,663 bytes in 301 blocks.
==21669== still reachable: 8,921,579 bytes in 79,926 blocks.
==21669== suppressed: 0 bytes in 0 blocks.
==21669== Rerun with --leak-check=full to see details of leaked memory.
==21656== Invalid read of size 1
==21656== at 0x4C21F92: strlen (mc_replace_strmem.c:242)
==21656== by 0x7C521DF: puts (in /lib/libc-2.7.so)
==21656== by 0x1A8B253C: (within /usr/lib/pidgin/xchat-chats.so)
==21656== by 0x1A8B28DD: (within /usr/lib/pidgin/xchat-chats.so)
==21656== by 0x6B6891B: purple_conversation_new (in
/usr/lib/libpurple.so.0.4.3)
==21656== by 0x6B89565: serv_got_joined_chat (in /usr/lib/libpurple.so.0.4.3)
==21656== by 0x1EC02E79: (within /usr/lib/purple-2/libmsn.so)
==21656== by 0x1EBF06EC: msn_cmdproc_process_cmd (in
/usr/lib/purple-2/libmsn.so)
==21656== by 0x1EBFE032: (within /usr/lib/purple-2/libmsn.so)
==21656== by 0x4651BD: (within /usr/bin/pidgin)
==21656== by 0x74C478A: g_main_context_dispatch (in
/usr/lib/libglib-2.0.so.0.1600.6)
==21656== by 0x74C7F5C: (within /usr/lib/libglib-2.0.so.0.1600.6)
==21656== Address 0x0 is not stack'd, malloc'd or (recently) free'd
Pidgin 2.4.3 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.
If you can reproduce the crash, please notify the developers
by reporting a bug at:
http://developer.pidgin.im/simpleticket/
Please make sure to specify what you were doing at the time
and post the backtrace from the core file. If you do not know
how to get the backtrace, please read the instructions at
http://developer.pidgin.im/wiki/GetABacktrace
If you need further assistance, please IM either SeanEgn or
LSchiere (via AIM). Contact information for Sean and Luke
on other protocols is at
http://developer.pidgin.im/wiki/DeveloperPages
GtkVBox
GtkVBox
==21656==
==21656== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1466 from 4)
==21656== malloc/free: in use at exit: 12,874,138 bytes in 120,970 blocks.
==21656== malloc/free: 1,184,601 allocs, 1,063,631 frees, 197,814,014 bytes
allocated.
==21656== For counts of detected errors, rerun with: -v
==21656== searching for pointers to 120,970 not-freed blocks.
==21656== checked 17,568,928 bytes.
==21656==
==21656== LEAK SUMMARY:
==21656== definitely lost: 838,165 bytes in 14,700 blocks.
==21656== possibly lost: 610,895 bytes in 589 blocks.
==21656== still reachable: 11,425,078 bytes in 105,681 blocks.
==21656== suppressed: 0 bytes in 0 blocks.
==21656== Rerun with --leak-check=full to see details of leaked memory
$
==============================
Greets
Mirko
--- End Message ---
--- Begin Message ---
Closing as this bug is fixed upstream since at least version 2.6.3.
--- End Message ---
