[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10186 [Tor]: Backtrace support for windows
#10186: Backtrace support for windows
-----------------------------+--------------------------------
Reporter: nickm | Owner:
Type: enhancement | Status: needs_revision
Priority: normal | Milestone: Tor: 0.2.5.x-final
Component: Tor | Version:
Resolution: | Keywords: tor-client windows
Actual Points: | Parent ID: #11046
Points: |
-----------------------------+--------------------------------
Comment (by cypherpunks):
>We need to use StackWalk64, disable FPO
Yes.
>and get symbols using... something.
Not for now.
>Have you seen âhttps://code.google.com/p/backtrace-mingw/ ? Does it work?
Is it good? Can we take ideas from it?
It using the same StackWalk64, just resolves addresses with debug
information generated by GCC using specific libs. Overcomplex mix by run-
time code and size of result.
Better to have proper stack trace with valid RVAs that user could to
report. For proper resolve address-to-function-name we could to use gdb
(at least it worked for mingw port) during investigation a bug. Debug info
with symbols can be saved per package, like gitian-based builder does it
for linux bundles now.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10186#comment:13>
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