Bitlbee crashed with

[Jens Sülwald <jsuelwald@…>]

If i connect to bitlbee and login with my Password as long as i've already connected to it, it crashed. I'm running this thing in daemon mode and i think it has something to do with jabber-chatrooms on autoconnect.

This behaviour can be reproduced here, using the latest development-snapshot.

Program terminated with signal 11, Segmentation fault.
[New process 23102]
#0  0x00000000057d2ed5 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00000000057d2ed5 in raise () from /lib/libc.so.6
#1  0x0000000000420719 in sighandler (signal=11) at unix.c:205
#2  <signal handler called>
#3  0x0000000004c22a81 in _vgrZU_libcZdsoZa_index (s=0x0, c=47) at mc_replace_strmem.c:160
#4  0x000000000043203d in jabber_chat_pkt_presence (ic=0x6783750, bud=0x6e5d500, node=0x6e66490) at conference.c:285
#5  0x0000000000437be8 in jabber_pkt_presence (node=0x6e66490, data=0x6783750) at presence.c:118
#6  0x00000000004284a9 in xt_handle (xt=0x6e22fd0, node=0x6e66490, depth=0) at xmltree.c:191
#7  0x0000000000428329 in xt_handle (xt=0x6e22fd0, node=0x6e33190, depth=1) at xmltree.c:171
#8  0x00000000004282e6 in xt_handle (xt=0x6e22fd0, node=0x0, depth=1) at xmltree.c:167
#9  0x00000000004327fc in jabber_read_callback (data=0x6783750, fd=20, cond=GAIM_INPUT_READ) at io.c:177
#10 0x000000000042240e in gaim_io_invoke (source=0x6e078d0, condition=G_IO_IN, data=0x6e07890) at events_glib.c:84
#11 0x000000000526678b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x0000000005269f5d in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x000000000526a48d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#14 0x000000000042239c in b_main_run () at events_glib.c:63
#15 0x000000000042054a in main (argc=4, argv=0x7ff000c08) at unix.c:135
(gdb)

[wilmer]

This is fixed a little while ago, can't pin-point the exact changeset ATM.