- Jun 13, 2016
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- Jun 12, 2016
-
-
Andrea Shepard authored
-
Roger Dingledine authored
-
Karsten Loesing authored
-
- Jun 11, 2016
-
-
Nick Mathewson authored
FreeBSD uses _Generic() in its system headers, and is within its rights to do so.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
This is a big-ish patch, but it's very straightforward. Under this clang warning, we're not actually allowed to have a global variable without a previous extern declaration for it. The cases where we violated this rule fall into three roughly equal groups: * Stuff that should have been static. * Stuff that was global but where the extern was local to some other C file. * Stuff that was only global when built for the unit tests, that needed a conditional extern in the headers. The first two were IMO genuine problems; the last is a wart of how we build tests.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
This gives more accurate results under Clang, which can only help us detect more warnings in more places. Fixes bug 19216; bugfix on 0.2.0.1-alpha
-
Nick Mathewson authored
-
Nick Mathewson authored
IMO it's fine for us to make exceptions to this rule in the unit tests, but not in the code at large.
-
Nick Mathewson authored
This warning triggers on silently promoting a float to a double. In our code, it's just a sign that somebody used a float by mistake, since we always prefer double.
-
Nick Mathewson authored
This caught quite a few minor issues in our unit tests and elsewhere in our code.
-
Nick Mathewson authored
This caused a trivial warning in curve25519-donna-64bit.h, which had two unused constants. I commented them out.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
This warning, IIUC, means that the compiler doesn't like it when it sees a NULL check _after_ we've already dereferenced the variable. In such cases, it considers itself free to eliminate the NULL check. There are a couple of tricky cases: One was the case related to the fact that tor_addr_to_in6() can return NULL if it gets a non-AF_INET6 address. The fix was to create a variant which asserts on the address type, and never returns NULL.
-
Nick Mathewson authored
-
- Jun 09, 2016
-
-
Andrea Shepard authored
-
- Jun 07, 2016
-
-
George Kadianakis authored
-
- Jun 06, 2016
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Coverity noticed that we check tor_sscanf's return value everywhere else.
-
- Jun 02, 2016
-
-
Nick Mathewson authored
Previously, we used !directory_fetches_from_authorities() to predict that we would tunnel connections. But the rules have changed somewhat over the course of 0.2.8
-
Nick Mathewson authored
Fixes the 0.2.9 instance of bug #19213, which prevented mingw64 from working. This case wasn't in any released Tor.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Fixes the 0.2.7 case of bug #19213, which prevented mingw64 from working.
-