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

Re: [tor-bugs] #3274 [Tor Client]: segmentation fault when setting "StrictNodes 1" in torrc

#3274: segmentation fault when setting "StrictNodes 1" in torrc
------------------------+---------------------------------------------------
 Reporter:  mr-4        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client  |        Version:  Tor: 0.2.2.27-beta
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by nickm):

 ok.  So the idea is to make Tor produce a core dump file when it crashes,
 then use gdb to extract a stack trace from that core dump.

 It's easiest to get a core dump if you're not running it as a service: if
 you can this crash from the command line, that'll be easiest.  To get a
 core dump, run "ulimit -c unlimited" in bash before you start Tor.
 (That's "unlimit coredumpsize" if you use tcsh.)  Then after Tor crashes,
 it should produce a core file.  ''Don't send us the core file'' -- it has
 keys and sensitive data in it.  Just run "gdb TOR CORE" where TOR is the
 path to your Tor executable, and CORE is a path to the core file.  gdb
 will load the core.  To get a stack trace, say "bt".  gdb will print a
 back trace.  Copy this verbatim into the bug report.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3274#comment:8>
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