BUG: jabberd-2.0s4 causes bus error under Tiger

[tonyarnold@…]

The current version of the Jabber Daemon (2.0s4) in DP does not work under Tiger. The router service starts OK, but then when trying to execute the next tool in the chain (c2s), router throws a bus error. I have also tried (after having the error above with the DP version) compiling the latest jabberd (2.0s8) myself with full debugging and still get the same error. Here is a gdb backtrace of the darwinports version:

Powerbook:~ tony$ gdb router GNU gdb 6.1-20040303 (Apple version gdb-384) (Mon Mar 21 00:05:26 GMT 2005) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-apple-darwin"...Reading symbols for shared libraries ........ done

(gdb) run -D Starting program: /opt/jabberd/bin/router -D Reading symbols for shared libraries .++ done WARN: Debugging not enabled. Ignoring -D.

Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x90003248 in strlen () (gdb) bt #0 0x90003248 in strlen () #1 0x0000e8f8 in nad_find_scoped_namespace (nad=0x301310, uri=0x386e8 "​http:// etherx.jabber.org/streams", prefix=0x0) at nad.c:358 #2 0x0000eff0 in nad_add_namespace (nad=0x301310, uri=0x386e8 "​http://etherx.jabber.org/ streams", prefix=0x388ac "stream") at nad.c:544 #3 0x0000838c in _sx_server_notify_header (s=0x300c40, arg=0x80808080) at server.c:49 #4 0x00006c24 in sx_can_write (s=0x300c40) at io.c:327 #5 0x00005a88 in router_mio_callback (m=0x300ba0, a=2155905152, fd=16, data=0x0, arg=0x300bb0) at router.c:855 #6 0x0000d7f4 in mio_write (m=0x300ba0, fd=16) at mio.c:338 #7 0x00004838 in _router_sx_callback (s=0x300c40, e=2155905152, data=0x0, arg=0x300bb0) at router.c:499 #8 0x00009e90 in sx_event (file=0x0, line=-2139062144, s=0x300c40, e=2155905152, data=0xffffffff) at sx.c:325 #9 0x00006a20 in sx_can_read (s=0x300c40) at io.c:218 #10 0x00005a70 in router_mio_callback (m=0x300ba0, a=2155905152, fd=16, data=0x0, arg=0x300bb0) at router.c:847 #11 0x0000dbcc in mio_run (m=0x300ba0, timeout=-2139062144) at mio.c:261 #12 0x00003d10 in main (argc=5347, argv=0x3346c) at main.c:408 (gdb)

[jmpp@…]

Assigning bug to maintainer of port.

-jmpp

[toby@…]

What exactly do I do to reproduce this crash?

Also, looks like router is sitting in poll when I first run it... Tiger's poll is pretty broken. :-\

[tonyarnold@…]

Hi Toby - you don't actually need to do anthing - it just won't start at all. I was trying to start the services individually to find out what was wrong, so I ran:

router -D c2s -D

Router started OK, but as soon as c2s tried to use it, router throws a bus error.

[toby@…]

I've committed an update to 2.0s8 and a change to force the use of select(). This *should* fix the crash... let me know.

Run 'port sync' and try reinstalling. Note that there's a delay in the CVS->rsync mirroring.

[tonyarnold@…]

OK, further, but still no go:

Powerbook:~ tony$ jabberd -D JBRD: debug on JBRD: version(2.0s8) JBRD: config_dir(/opt/darwinports/etc/jabberd) JBRD: LaunchJob: router -> /opt/darwinports/bin/router -c /opt/darwinports/etc/jabberd/router.xml - D JBRD: LaunchJob: resolver -> /opt/darwinports/bin/resolver -c /opt/darwinports/etc/jabberd/ resolver.xml -D JBRD: LaunchJob: sm -> /opt/darwinports/bin/sm -c /opt/darwinports/etc/jabberd/sm.xml -D JBRD: LaunchJob: s2s -> /opt/darwinports/bin/s2s -c /opt/darwinports/etc/jabberd/s2s.xml -D JBRD: LaunchJob: c2s -> /opt/darwinports/bin/c2s -c /opt/darwinports/etc/jabberd/c2s.xml -D ROUT: Sat May 7 20:44:28 2005 [notice] starting up RSLV: Sat May 7 20:44:28 2005 [notice] starting up RSLV: sx (sasl.c:549) initialising sasl plugin S2S : Sat May 7 20:44:28 2005 [notice] starting up (interval=60, queue=60, keepalive=0, idle=86400) C2S : Sat May 7 20:44:28 2005 [notice] starting up ROUT: Sat May 7 20:44:28 2005 [info] process id is 13522, written to /opt/darwinports/var/jabberd/ pid/router.pid RSLV: Sat May 7 20:44:28 2005 [info] process id is 13523, written to /opt/darwinports/var/jabberd/ pid/resolver.pid ROUT: Sat May 7 20:44:28 2005 user.c:34 loading user table RSLV: Sat May 7 20:44:28 2005 scod.c:40 creating new scod context S2S : Sat May 7 20:44:28 2005 [info] process id is 13525, written to /opt/darwinports/var/jabberd/ pid/s2s.pid C2S : Sat May 7 20:44:28 2005 [info] process id is 13526, written to /opt/darwinports/var/jabberd/ pid/c2s.pid S2S : sx (sasl.c:549) initialising sasl plugin ERROR: c2s died. Shutting down server. JBRD: Got a signal... pass it on. JBRD: It was a TERM. Shut it all down! Powerbook:~ tony$

[toby@…]

Committed 2.0s9, still broken?

[toby@…]

No response, closing.