Modify

#806 closed defect (moreinfo)

bitlbee with otr crash

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

Description

  1. I had a conversation with a user days ago. They sign off.
  1. Today, they send me a message that is unencrypted (whitespace).
  1. Not sure if this part is related...

"otr disconnect <misspelled username>" "<misspelled username>: hi" And I get "<misspelled username>: unknown user"

  1. Then I send a real message to them and get this:

otr: OTR Error: You sent encrypted data to ...

Then bitlbee crashed.

Attachments (0)

Change History (2)

comment:1 Changed at 2011-07-29T07:29:25Z by pesco

Component: BitlBeeOTR
Owner: set to pesco

comment:2 Changed at 2011-10-06T20:30:26Z 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/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.

Modify Ticket

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