mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-11 05:33:47 +01:00
bf0e2ae0d0
This is the very first tracepoint in tor. It is in the circuit subsystem for when a new circuit opens. LTTng instrumentation requires lot more around a tracepoint than USDT thus this commit only adds one tracepoint in order to outline a base to add more tracepoints later. The idea is that we separate subsystem into what LTTng defines as "providers" so the circuit provider contains the tracepoint definitions for the circuit subsystem. Signed-off-by: David Goulet <dgoulet@torproject.org> Signed-off-by: David Goulet <dgoulet@torproject.org> |
||
|---|---|---|
| .. | ||
| testdata | ||
| .enable_practracker_in_hooks | ||
| exceptions.txt | ||
| includes.py | ||
| metrics.py | ||
| practracker_tests.py | ||
| practracker.py | ||
| problem.py | ||
| README | ||
| test_practracker.sh | ||
| util.py | ||
Practracker is a simple python tool that keeps track of places where our code is ugly, and tries to warn us about new ones or ones that get worse. Right now, practracker looks for the following kinds of best-practices violations: .c files greater than 3000 lines long .h files greater than 500 lines long .c files with more than 50 includes .h files with more than 15 includes All files that include a local header not listed in a .may_include file in the same directory, when that .may_include file has an "!advisory" marker. The list of current violations is tracked in exceptions.txt; slight deviations of the current exceptions cause warnings, whereas large ones cause practracker to fail. For usage information, run "practracker.py --help".