Bitlbee 3.2 can be installed with a 3.0 otr plugin

[bitlbee@…]

I'm running Debian Wheezy (which is the current stable, if I'm not mistaken) and have installed bitlbee from ​http://code.bitlbee.org/debian/devel/wheezy/amd64/bitlbee_3.2+20130623+devel+994-1_amd64.deb and ​http://code.bitlbee.org/debian/devel/wheezy/amd64/bitlbee-common_3.2+20130623+devel+994-1_all.deb. While filing this bug, I found out those were the only packages I installed, and I still was running the 3.0 OTR package. Needless to say, that lead to segfaults. I'm leaving the segfault data attached here, not that I think it's useful now I've found the cause.

Anyway, i think it's a good idea to modify the bitlbee debs to make them say they're incompatible with a otr plugin <3.2; that'd save other people the hassle I've been going through.

---8<--- Problem description of the segfault:

The problem is that Bitlbee starts up correctly, I can login and receive Twitter-messages, but as soon as I try to message someone (at least over msn or icq), bitlbee segfaults.

The backtrace in gdb indicates a problem in the otr subsystem. I've pasted the backtrace here, and the core file is attached to this ticket too.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff56a5d04 in keygen_in_progress () from /usr/lib/bitlbee/otr.so
(gdb) generate-core-file /tmp/bitlbee-crash.core
Saved corefile /tmp/bitlbee-crash.core
(gdb) bt
#0  0x00007ffff56a5d04 in keygen_in_progress () from /usr/lib/bitlbee/otr.so
#1  0x00007ffff56a2a24 in op_policy () from /usr/lib/bitlbee/otr.so
#2  0x00007ffff5494036 in otrl_message_sending () from /usr/lib/libotr.so.2
#3  0x00007ffff56a2807 in otr_filter_msg_out () from /usr/lib/bitlbee/otr.so
#4  0x00007ffff7f948c7 in bee_irc_user_privmsg_cb (data=<optimized out>, 
    fd=<optimized out>, cond=<optimized out>)
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/irc_im.c:456
#5  0x00007ffff7f94a24 in bee_irc_user_privmsg (iu=0x7ffff82b8d70, 
    msg=0x7ffff83372af "test")
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/irc_im.c:435
#6  0x00007ffff7f9260e in irc_process (irc=0x7ffff821e5c0)
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/irc.c:395
#7  0x00007ffff7f8dfd8 in bitlbee_io_current_client_read (data=0x7ffff821e5c0, 
    fd=13, cond=<optimized out>)
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/bitlbee.c:226
#8  0x00007ffff7fa2731 in b_event_passthrough (fd=13, event=<optimized out>, 
    data=0x7ffff821e680)
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/lib/events_libevent.c:147
#9  0x00007ffff7440344 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#10 0x00007ffff7fa2ab8 in b_main_run ()
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/lib/events_libevent.c:86
#11 0x00007ffff7fa04e5 in main (argc=<optimized out>, argv=0x7fffffffecc8)
    at /tmp/buildd/bitlbee-3.2+20130623+devel+994/unix.c:183

[Wilmer van der Gaast <wilmer@…>]

Argh, that's annoying. I thought I had those deps already, will check.

[dx]

Just checked ./debian/control and it seems to be fixed now.