Hello
I spent the last two weeks implementing the network status document parser
and the microdescriptor consensus parser. The network status document
parsing code is ready for review here[1]. It's a fairly large amount of
code, with ~1.4K new LoC. The microdescriptor consensus parser is much
simp
On 08/06/2012 07:03 PM, Nick Mathewson wrote:
Hm. Tor itself doesn't have a tcmalloc compilation option, so whatever
it's doing is something freebsd added. To debug this kind of thing,
what I usually suggest is to rebuild and look carefully at which
compiler and linker options are used in build
Hm. Tor itself doesn't have a tcmalloc compilation option, so whatever
it's doing is something freebsd added. To debug this kind of thing, what I
usually suggest is to rebuild and look carefully at which compiler and
linker options are used in building Tor, and see if they include the
appropriate
Hi Damian,
Looking at coverage the test provides, I was under the impression that the
various cases of include_fields and exclude fields (e.g. if they overlap)
should also be tested, but if you find that unnecessary, that would help
explain why my unit tests were difficult to follow.
In the mocki
Hi,
I posted this message in tor-relays, but it seems to me (and another
people) that dev mail-list is better channel to use.
Thanks!
Original Message
Hi all,
From time to time my tor node (minibofh) stopped to work properly;
since it's a tiny FreeBSD VPS, the root origin w
