Mercurial > pidgin
view gaim.pc.in @ 15786:b25acae693cd
Change connection.c:gaim_connection_error() to still work even if the
message parameter is NULL. There's no reason to error-out of that
function just because some yuppie didn't pass us an error message.
But we still log a critical message, so those of you at home running
with fatal_criticals will still crash.
I noticed this because Jabber isn't handling <stream:error/> correctly
right now. Anyone else notice this? The code is written to look for
"stream:error", but our xmlnode stuff just sees "error" (even though
the "stream:error" format is sent over the wire). I think it's
because of the libxml change.
To reproduce the problem, sign onto the same resource twice and note
that the error message that Gaim gives you sucks.
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Tue, 13 Mar 2007 07:33:08 +0000 |
| parents | 32f954e8d8aa |
| children | c6e563dfaa7a |
line wrap: on
line source
prefix=@prefix@ exec_prefix=@exec_prefix@ libdir=@libdir@ includedir=@includedir@ datarootdir=@datarootdir@ datadir=@datadir@ sysconfdir=@sysconfdir@ Name: Gaim Description: Gaim is a GTK2-based instant messenger application. Version: @VERSION@ Requires: glib-2.0 Cflags: -I${includedir}/gaim Libs: -L${libdir} -lgaim