OTR crashing in newest bzr

[wilmer]

pesco, it looks like sometihng went wrong in your last changes. Several people in #bitlbee reported crashes. Someone's trying to get a backtrace now.

[anonymous]

BitlBee 3.0.3+devel+807-1 backtrace

[wilmer]

That backtrace is useless, it shows a trace of what BitlBee was doing when you attached the debugger, I guess I didn't explain that well enough. :-/

So what you need to do is the gdb command you used, then first "c" to tell it to keep running, then bt once it actually crashes.

[wilmer]

Oh yes, pesco, AFAIK the crashes happen when receiving non-encrypted msgs, but not sure.

[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.