Re: [tor-bugs] #9299 [Tor]: Dump stack traces on assertion, crash, or general trouble

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9299: Dump stack traces on assertion, crash, or general trouble
---------------------------------+------------------------------------------
 Reporter:  nickm                |          Owner:                    
     Type:  enhancement          |         Status:  new               
 Priority:  normal               |      Milestone:  Tor: 0.2.5.x-final
Component:  Tor                  |        Version:                    
 Keywords:  tor-relay debugging  |         Parent:                    
   Points:                       |   Actualpoints:                    
---------------------------------+------------------------------------------
Description changed by nickm:

Old description:

> It's so easy to dump stack traces these days!
>
> I have a "backtrace" branch right now that an dump stack traces on
> assertion failures.  It works on glibc/ELF, and on OSX.  We should expand
> it to work on Windows too, and BSD if we can.
>
> Other fixes to make before it's ready:
>   * It should be able to log a stack trace too.
>     * It should log the stack trace on an assertion.
>   * There should be an option to tell it not to log to the stack_dumps
> file, perhaps.
>   * Perhaps the logfile should be pid-controlled?
>   * It should support Windows.
>   * It should handle deadly signals (SEGV, etc) as well.
>   * It should indicate to the user somehow (if it can) that stuff might
> be saved to the stack_dumps file.
>   * It should have tests.

New description:

 It's so easy to dump stack traces these days!

 I have a "backtrace" branch right now that an dump stack traces on
 assertion failures.  It works on glibc/ELF, and on OSX.  We should expand
 it to work on Windows too, and BSD if we can.

 Other fixes to make before it's ready:
   * ~~It should be able to log a stack trace too.~~
     * ~~It should log the stack trace on an assertion.~~
   * ~~There should be an option to tell it not to log to the stack_dumps
 file, perhaps.~~
   * ~~Perhaps the logfile should be pid-controlled?~~
   * It should support Windows.
   * ~~It should handle deadly signals (SEGV, etc) as well.~~
   * ~~It should indicate to the user somehow (if it can) that stuff might
 be saved to the stack_dumps file.~~
   * It should have tests.

--

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