[JDEV] Got the AIM Transport to SEGFAULT!

Charles Forsythe forsythe at netvoice.net
Fri Dec 15 00:17:59 CST 2000


First a not about the MX record issue:

Mark Hahn wrote:
>However, now that I have fixed that little bug, the server is
>looking for MX records associated with the transport IP address I
>assume.

I figured out that this happens when the aim-transport can't connect to
the port.  At first, I had aim.moe.netvoice.net == moe.netvoice.net. 
This is a public address and so even though I'm coming FROM moe TO moe,
the connection tries to go through the firewall, which blocks incoming
traffic on 7009.  I changed the DNS record for aim.moe.netvoice.net to
be the internal private IP address of moe (10.x.x.x) , so that the
traffic doesn't leave the LAN and that works fine.  Setting
aim.moe.netvoice.net to resolve to 127.0.0.1 would probably also fix the
problem.

Now my NEW PROBLEM:
-------------------------------------------------------------------------
Fri Dec 15 00:08:06 2000  debug/tstream.c:247 tstream read event
Fri Dec 15 00:08:06 2000  debug/xmlstream.c:228 xmlstream_main: startup
Fri Dec 15 00:08:06 2000  debug/etherxs.c:91 got node from etherx!
Fri Dec 15 00:08:06 2000  debug/external.c:32 [AIM] We got a packet from
etherx
Fri Dec 15 00:08:06 2000  debug/pres.c:19 [AIM] Starting a new session!

Fri Dec 15 00:08:06 2000  debug/auth.c:46 [AIM] Auth recevied for
<registered name='AOLScreenName' pass='aolpass'>
Fri Dec 15 00:08:06 2000  debug/auth.c:10 [AIM] Sleeping on
test1 at moe.netvoice.net/work

Fri Dec 15 00:08:08 2000  debug/sessions.c:480 [AIM] New session for
AOLScreenName using aolpass, jid set to test1 at moe.netvoice.net/work

aim_conn_addhandler: adding for ffff/0005
aim_conn_addhandler: adding for ffff/0004
aim_conn_addhandler: adding for 0017/0007
aim_conn_addhandler: adding for 0017/0003
Fri Dec 15 00:08:08 2000  debug/sessions.c:587 [AIM] In our main session

Fri Dec 15 00:08:08 2000  debug/sessions.c:590 [AIM] Got data from the
select: -1
Fri Dec 15 00:08:08 2000  debug/sessions.c:643 [AIM] Closing up a main
thread

Memory Leak! [pmalloc received NULL pool, unable to track allocation,
exiting]
Aborted (core dumped)
-------------------------------------------------------------------------

Anyone?

-- Charles




More information about the JDev mailing list