#9754: Tor 0.2.4.17-rc crashed with failed assertion
------------------------------+--------------------------------
Reporter: communicator | Owner:
Type: defect | Status: needs_information
Priority: major | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version: Tor: unspecified
Resolution: | Keywords: tor-relay
Actual Points: | Parent ID:
Points: |
------------------------------+--------------------------------
Comment (by andrea):
Replying to [comment:13 nickm]:
> Agreed; running it under valgrind would maybe get some useful results.
>
> Is there any more debugging/logging code that would help figure out
what's going on?
I think valgrind would be the most useful thing. Also, it'd be nice to
see how this binary was built and if anything changes if built with -O0;
since that line doesn't look like there's any very clear possible cause,
and the circuitmux.c in the Debian repo matches ours, I'd be curious to
see if the actual crash was elsewhere and the optimizer has confused
things. Since so far the exact site of the crash seems nondeterministic,
though, we may not see this again if the reporter re-runs with a different
build.
> Also:
> >Where can I find whatever extra patches Debian is adding?
>
> https://gitweb.torproject.org/debian/tor.git
Thanks
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9754#comment:14>
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