I filed the bug 76082 with Red Hat. From what I understand from looking at the information on the related bug, it seems like this is hitting a buffer that is too small or the threads in pth don't have large enough stacks set up (or something like that).

I did not try they patched version of glibc rather I downgraded to the prior version (2.2.4-29) which fixed the problem as well.

Any AOL transport developers want to take a look at fixing this? Red Hat is putting out a new version of glibc to stop the crashing, but if there is code that isn't setting up buffers/stacks properly it would be worth fixing.


From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JDEV] Segfault/Dynamic linking Issue with AIM Transport
Date: Mon, 21 Oct 2002 17:36:39 +0200 (CEST)

On Wed, 16 Oct 2002 [EMAIL PROTECTED] wrote:

>> I ran into a strange problem with the AOL transport version
>> aim-transport-stable-20020711. I am running the transport out-of-process
>> and connecting it to jabber 1.4.2. What happens is that when ever I attempt
>> to talk to the gateway (either registering the gateway or sending a message)
>> the AOL process either gives a seg fault or dies with an error about not
>> being able to resolve the htons function (a dynamic linking error).
>> The system is running Red Hat 7.1 and I had just applied the glibc update
>> (2.2.4-30) for the resolver issue

See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=76082
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75128
ftp://people.redhat.com/jakub/glibc/errata/

These inofficial packages work for me.

Regards

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

_________________________________________________________________
Broadband?�Dial-up? Get reliable MSN Internet Access. http://resourcecenter.msn.com/access/plans/default.asp

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to