[Pidgin] #11550: XMPP/SASL authentication fail
Pidgin
trac at pidgin.im
Sun Apr 25 01:04:15 EDT 2010
#11550: XMPP/SASL authentication fail
---------------------+------------------------------------------------------
Reporter: fangism | Owner: deryni
Type: defect | Status: pending
Milestone: | Component: XMPP
Version: 2.6.6 | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Changes (by darkrain42):
* status: new => pending
Comment:
So I don't really know at all why this would be happening (and only on one
arch, although I wonder if the 10.4 vs 10.6 is the issue), but the best I
can imagine is that some other code is using libsasl, but cleaning up
twice (thus leaking libpurple's reference).
To debug:
* Make sure libsasl2 and libjabber/libxmpp are built with debug
symbols/not stripped
* Run Pidgin in gdb, but before starting, add breakpoints ("`break
<x>`") on `sasl_client_init`, `sasl_server_init`, `sasl_done`,
`sasl_client_new`, and (if possible) client.c:client_done.
* Run (and try to log in to an XMPP account) and get a `bt full` (full
backtrace) each time gdb stops, and then type 'continue' to keep running.
* If the breakpoint is `sasl_client_new` or `sasl_client_init`,
print the value ("`p <x>`") of `_sasl_client_active`
And then attach the entire transcript of that.
--
Ticket URL: <http://developer.pidgin.im/ticket/11550#comment:23>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list