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

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

#9299: Dump stack traces on assertion, crash, or general trouble
-----------------------------+---------------------------------
     Reporter:  nickm        |      Owner:
         Type:  enhancement  |     Status:  closed
     Priority:  normal       |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor          |    Version:
   Resolution:  implemented  |   Keywords:  tor-relay debugging
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+---------------------------------

Comment (by cypherpunks):

 Stack trace unreadable if FPO enabled in general or used optimization
 options (then FPO applied selectively by compiler depends function's code)
 for x86 platform. It's not problem for x86_64 because GCC generates unwind
 tables there by default.
 If to enable unwind tables unconditionally by "-fasynchronous-unwind-
 tables" then stack trace readable with any optimizations.

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