Bitlbee disconnects on receiving an OTRed message

[wgreenhouse]

am using the code.bitlbee.org repositories for Debian Squeeze; this bug appeared in version 3.0.3+devel+803-1.

When I receive an OTR message from a buddy, a message from root appears in the control channel, such as "conversation with [nick] is now on the record (trusted)" and I will receive the message, but then I will be immediately disconnected from the server. If I then reconnect, I will see that they've been trying to talk to me, and I will see the usual "The encrypted message received from [nick] is unreadable, as you are not currently communicating privately" that one sees when an OTR session expires. However, if I try to initiate a new OTR session (such as asking them what they said last time), I am again disconnected when they try to reply.

So far, I have only been able to test this with one person on my buddy list, who is using Adium on Mac OS X Leopard.

[pesco]

sounds like a segfault. we need a stacktrace at the point of crash to properly diagnose the cause. the easiest way to get one would be to attach gdb to the running bitlbee process. like so:

$ script bitlbee-trace.txt                 # record this session
$ ps aux | grep bitlbee
17920 ?        Ss     0:02 bitlbee         # <-- note process ID
[...]
$ sudo gdb -quiet `which bitlbee` 17920
[...]
(gdb) continue
[... reproduce the crash ...]

Program received signal SIGSEGV, Segmentation fault.
0x00007fe3c03050d8 in poll () from /lib/libc.so.6
(gdb) bt
[... HERE COMES THE STACKTRACE ...]
(gdb) detach
(gdb) quit
$ exit

then attach bitlbee-trace.txt to this ticket.

NB: if you can, do it with a debug build of bitlbee, i.e. one built with ./configure --debug=1.