C tools =
Formatting ==
Lindent, reformat C code to the Linux kernel (and osmocom) coding standards¶

Patches¶

git format-patch -1, generate a patch

checkpatch.pl, check patches for common errors (Ignore x-signed-off-by)

make distcheck - this catches quite a few errors, run it before sending patches.

git send-email -1 Send a patch to the mailing list (after configuration)

Testing¶

make check - run it and don't introduce regressions

Misc¶

pahole (dwarves), http://www.ohloh.net/p/pahole See the memory layout of structures

gdb, debugging

valgrind, http://valgrind.org/, dynamic analysis of memory management/threading

mudflap (gcc option), check array/pointer accesses. See http://zecke.blogspot.com/2012/10/know-your-tools-mudflap.html

Python tools =
Formatting ==
pep8, https://pypi.python.org/pypi/pep8 Check formatting for pep8 compliance¶

autopep8, https://github.com/hhatto/autopep8 Reformat code to be pep8-complient

Checking/analysis¶

pyflakes, https://pypi.python.org/pypi/pyflakes Statically find some errors