Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #9602

Closed (moved)
(moved)
Open
Created Aug 27, 2013 by Trac@tracbot

Segfault in Tor 0.2.4.1[67]-rc after SIGUSR1

I experienced an segfault after I upgraded my Tor to 0.2.4.16-rc.

The log entries before this follows:

Aug 27 04:40:02 tor kernel: [8051709.437719] grsec: From 38.229.70.34: Segmentation fault occurred at (nil) in /usr/bin/tor[tor:21268] uid/euid:220/220 gid/egid:220/220, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 Aug 27 04:40:02 tor kernel: [8051709.437663] tor![21268] general protection !ip:54fda6ae !sp:5e4e0eb0 !error:0 in libc-2.15.so[54f94000+17e000]

It was probably after SIGUSR1 to the process.

Unfortunately I don't have any more details about this, as it has happened only once so far. Before this, I've been running 0.2.3.25 for quite a while without any problems.

Trac:
Username: pyllyukko

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