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