Opened 12 years ago

Last modified 8 years ago

#695 closed defect (User disappeared)

Tor crashing with a bus error

Reported by: ricoxx Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: ricoxx, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


TOR, compiled on Debian Etch/Sparc with standard parameters consitently crashes with a Bus Error after setting up circuits.
Before the crash, lots of messages like

Jun 08 07:29:47.798 [debug] conn_read_callback(): socket 19 wants to read.
Jun 08 07:29:47.798 [debug] read_to_buf_impl(): Read 996 bytes. 36354 on inbuf.
Jun 08 07:29:47.798 [debug] connection_dir_process_inbuf(): Got data, not eof. Leaving on inbuf.

are appearing.
The last message is always

Jun 08 07:29:47.799 [debug] conn_read_callback(): socket 13 wants to read.
Jun 08 07:29:47.799 [debug] read_to_buf_impl(): Read 229 bytes. 229 on inbuf.

suggesting perhaps a buffer underrun.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (6)

comment:1 Changed 12 years ago by computerguy12056

If you have recently installed a new driver or update pertaining to hardware, you may try a System Restore or uninstalling it!

comment:2 Changed 12 years ago by arma

Does Valgrind work on Debian/Sparc? If so, you should run Tor under it and see
what comes up.

Also, does also have this problem consistently?

comment:3 Changed 12 years ago by nickm

Are you still around? Does this still happen? If you're running this on debian, it would be great to use gdb
to get a backtrace for this, if it still occurs.

comment:4 Changed 12 years ago by nickm

Can't reproduce bug on information given; no contact with user since June. If you come back and this bug is
still happening, please mark it to get reopened, and we'll have another look.

comment:5 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:6 Changed 8 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.