#823 closed defect (moreinfo)

OTR crashing in newest bzr

Reported by: wilmer Owned by: pesco
Priority: major Milestone:
Component: OTR Version: devel
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


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.

Attachments (1)

bitlbee_bt.txt (4.6 KB) - added by anonymous at 2011-08-20T12:02:21Z.
BitlBee 3.0.3+devel+807-1 backtrace

Download all attachments as: .zip

Change History (4)

Changed at 2011-08-20T12:02:21Z by anonymous

Attachment: bitlbee_bt.txt added

BitlBee 3.0.3+devel+807-1 backtrace

comment:1 Changed at 2011-08-27T10:24:13Z by 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.

comment:2 Changed at 2011-08-27T10:24:46Z by wilmer

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

comment:3 Changed at 2011-10-06T20:31:05Z by pesco

Resolution: moreinfo
Status: newclosed

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/
(gdb) bt
(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.

Modify Ticket

as closed The owner will remain pesco.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.