An ecore loop based libpurple client...

Ka-Hing Cheung khc at hxbc.us
Tue Apr 14 19:34:27 EDT 2009


On Wed, 2009-04-15 at 01:24 +0200, "Marco Trevisan (Treviño)" wrote:
> Marco Trevisan (Treviño) wrote:
> > However during those days I've also fixed any other bug and now the
> > client (look at the attachment!) seems to work without any segmentation
> > fault, abort or any other error, however my connection troubles aren't
> > over yet. :/
> 
> I performed new tests after upgrading to ecore svn r39932 (which
> implemented the FD EBADF handling by Andre Dieb that fixes the
> fd-related aborts) but after some time (it can vary from few seconds to
> many minutes) that my client is connected to the prpl-msn protocol (I
> used the HTTP method) I get a crash due to a SIGPIPE exception.
> 
> It always happens after this request (could this be due to purple more
> than ecore?):

<snip>

> (23:15:33) gnutls: send failed: Error in the push function.
> 
> Program received signal SIGPIPE, Broken pipe.
> [Switching to Thread -1214285024 (LWP 30051)]
> 0xffffe410 in __kernel_vsyscall ()

Possibly, try applying
http://d.pidgin.im/viewmtn/revision/info/881df138362222308d7b078687b7576861609e9c

There were also various issues about gnutls that seems to go away when
nss is used, so maybe you can try that too.

-khc





More information about the Devel mailing list