[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9602 [Tor]: Segfault in Tor 0.2.4.1[67]-rc after SIGUSR1

#9602: Segfault in Tor 0.2.4.1[67]-rc after SIGUSR1
---------------------------+--------------------------------
     Reporter:  pyllyukko  |      Owner:
         Type:  defect     |     Status:  needs_information
     Priority:  normal     |  Milestone:  Tor: 0.2.4.x-final
    Component:  Tor        |    Version:  Tor: 0.2.4.16-rc
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |
---------------------------+--------------------------------

Comment (by pyllyukko):

 Replying to [comment:16 nickm]:
 > One more thing to consider: have you tried reproducing this while
 running Tor under valgrind? (See instructions in doc/HACKING for how to
 avoid spurious errors.) Often that can produce better stack traces than
 gdb for stack-corruption cases.

 I'm now trying with Valgrind, but now I'm unable to send the SIGUSR1 to
 Tor. Since it's not Tor's process but Valgrind's. Any ideas?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9602#comment:17>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs