Devtools » History » Version 5
Anonymous, 02/19/2016 10:47 PM
| 1 | 2 | = C tools = |
|
|---|---|---|---|
| 2 | == Formatting == |
||
| 3 | 1 | Lindent, reformat C code to the Linux kernel (and osmocom) coding standards |
|
| 4 | |||
| 5 | 2 | == Patches == |
|
| 6 | 1 | git format-patch -1, generate a patch |
|
| 7 | |||
| 8 | checkpatch.pl, check patches for common errors (Ignore x-signed-off-by) |
||
| 9 | |||
| 10 | 5 | make distcheck - this catches quite a few errors, run it before sending patches. |
|
| 11 | |||
| 12 | 1 | git send-email -1 Send a patch to the mailing list (after configuration) |
|
| 13 | 5 | ||
| 14 | 1 | ||
| 15 | 2 | == Testing == |
|
| 16 | 1 | make check - run it and don't introduce regressions |
|
| 17 | |||
| 18 | 2 | == Misc == |
|
| 19 | 1 | pahole (dwarves), http://www.ohloh.net/p/pahole See the memory layout of structures |
|
| 20 | |||
| 21 | gdb, debugging |
||
| 22 | |||
| 23 | valgrind, http://valgrind.org/, dynamic analysis of memory management/threading |
||
| 24 | |||
| 25 | 4 | mudflap (gcc option), check array/pointer accesses. See http://zecke.blogspot.com/2012/10/know-your-tools-mudflap.html |
|
| 26 | |||
| 27 | 2 | = Python tools = |
|
| 28 | == Formatting == |
||
| 29 | 1 | pep8, https://pypi.python.org/pypi/pep8 Check formatting for pep8 compliance |
|
| 30 | |||
| 31 | autopep8, https://github.com/hhatto/autopep8 Reformat code to be pep8-complient |
||
| 32 | 3 | ||
| 33 | == Checking/analysis == |
||
| 34 | pyflakes, https://pypi.python.org/pypi/pyflakes Statically find some errors |
