Difference between revisions of "Embedded Linux debugging/profiling/tracing tools - Overview"
m (moved (Embedded) Linux debugging/profiling/tracing tools - Overview to Embedded Linux debugging/profiling/tracing tools - Overview: Parens mess up catalog)
Revision as of 11:51, 25 January 2011
- (Embedded) Linux debugging/profiling/tracing tools - Overview
- Robert Berger
"If the only tool you have is a hammer all your problems are nails!"
There are quite a few tools for debugging/tracing/profiling user space/kernel/the whole GNU/Linux system. Still most people use printf() and friends due to a lack of knowledge what else is there and/or how to use it. I propose the creation of the centralized place to browse to if you want to find ways to debug your (Embedded) GNU/Linux system. A good place to publish such material would be the elinux wiki.
- gdb - http://www.gnu.org/software/gdb/
- oprofile - http://oprofile.sourceforge.net/news/
- kgdb/kdb - https://kgdb.wiki.kernel.org/index.php/Main_Page
- lttng - http://lttng.org/
- ftrace - https://rt.wiki.kernel.org/index.php/Ftrace
- gprof, gcov
... and many more ...
After the decision how/when and where (elinux wiki) this will be done I estimate it will take about 4 weeks to put some initial documents together, say on a Wiki. Afterwards this should be an open ended community effort.
As a professional trainer I would like to nominate myself to kick off the project and put up some initial pages which will also act as a template for others to contribute. For clarifications and further details contributors of the various projects are welcome to assist. This will also give them the opportunity to better present their projects to the community/public.