Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #695
Closed
Open
Created Jun 08, 2008 by Trac@tracbot

Tor crashing with a bus error

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]

Trac:
Username: ricoxx

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking