Created attachment 717046 [details]
Pidgin backtrace log
Description of problem:
Pidgin crashes when you run it.
Version-Release number of selected component (if applicable):
2.10.7-2.fc18 (libpurple 2.10.7)
Steps to Reproduce:
1. Run pidgin with sipe-based default profile
A ticket has been opened in pidgin bug ticketing system, however they claim it is the issue in sipe plugin.
The bug entry and backtrace doesn't contain enough information for me to work on this issue. I only see one function referenced from SIPE source code (sip-transport.c:1592) but without a version information I can't match it up the the source code visible to me.
- what is the version number of pidgin-sipe RPM installed on your machine?
- did you maybe compile pidgin-sipe yourself? If yes what release version or git commit?
- if you are not using latest 1.15.0 package from F18, can you reproduce the problem after upgrading?
- if you can still reproduce it with 1.15.0, can you provide a backtrace from a non-optimized version? E.g.
$ tar xf pidgin-sipe-1.15.0.tar.bz2
$ cd pidgin-sipe-1.15.0
$ CFLAGS="-g -O0" ./configure
-> install the generated libsipe.so as root
- if you can still reproduce it in the previous step, can you try to reproduce it the latest git HEAD?
and PLEASE PLEASE PLEASE run "pidgin --debug" and attach the log output too, so that I have some context where the crash actually happens.
Name : pidgin-sipe
Version : 1.15.0
Release : 1.fc18
I forgot to mention it here... pidgin -d runs without any issues.
(In reply to comment #3)
> I forgot to mention it here... pidgin -d runs without any issues.
This will make this difficult to debug. What is the log output without -d? And please try to reproduce with the non-optimized version.
I have sent you "with -d" by mail . Without it's just:
Pidgin 2.10.7-2.fc18 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.
A short summary of what we have discussed by mail:
Recompilation did not show any problematic areas. I am able to run "pidgin -n", and then log in manually. Pidgin does not crash. It only crashes when pidgin is trying to connect automatically after I run it.
At the moment I downgraded to purple-sipe and pidgin-sipe 1.13.3, as the problem appeared after upgrading to 1.15.0
Pushed proposed fix for inclusion in 1.15.1 release. Please verify.
Author: Stefan Becker <firstname.lastname@example.org>
Date: Wed Mar 27 17:47:28 2013 +0200
transport: fix use-after-free accesses
This is a proposed fix for the Heisenbug crash reported here:
Valgrind log showed invalid read/write accesses to the already freed
transport data structures in the following cases:
- sip: during redirect
- http: potentially on server initiated close
- http: on user initiated close
With this patch my valgrind log no longer shows any invalid accesses
from the SIP/HTTP input routines.
The patch has solved the issue, pidgin does not crash anymore.
pidgin-sipe-1.15.1-1.fc19 has been submitted as an update for Fedora 19.
pidgin-sipe-1.15.1-1.fc18 has been submitted as an update for Fedora 18.
pidgin-sipe-1.15.1-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pidgin-sipe-1.15.1-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
pidgin-sipe-1.15.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-sipe-1.15.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-sipe-1.15.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.