Editing Documentation/devtools/maemo5/valgrind

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

== Description ==

Valgrind is an Open Source suite of tools for debugging and profiling Linux programs. It works only on x86 (and PPC).

Valgrind is a really powerful and easy to use tool that can save you a lot of debugging time.

Because Valgrind works by simulating the x86 processor and instrumenting the binaries on the fly, it can control the program execution completely. As a downsize it makes program execution 10-300 times slower than normally, depending on the used Valgrind tools (massif is the fastest, callgrind the slowest) and can take a huge amount of memory.

The tools available for Valgrind are:

* ''Massif'': run-time memory usage graph and hyperlinked allocation backtraces (allocation are sorted by time*size)

* ''Memcheck'': Detects memory access errors (writes to freed memory, reads from uninitialized memory) and memory leaks (process has lost a pointer to allocation). This reports less false positives than any other (Open Source) tool and can call gdb when the error happens

* ''Cachegrind'': Performance profiling which can be started and stopped at any moment and the results can be sorted according to instructions, cache hits etc.

* ''Callgrind'': Like Cachegrind, but stores also callgraph information (but can show only instruction counts). Works very well with the Kcachegrind UI.<ref name="kcachegrindui">[http://kcachegrind.sourceforge.net/cgi-bin/show.cgi KCacheGrind]</ref>

* ''Helgrind'': Detects race conditions when (p)threaded programs access global data

=== Building Valgrind ===

Please note that in maemo environment we need to ''export G_SLICE="always-malloc"'' to avoid getting bogus leakage reports from Glib GSlice allocator (its TLS usage confuses Valgrind allocation tracking). If you build your own Valgrind version, you should use this setting when Valgrinding programs using Glib (e.g. all maemo UI apps).

== Packages ==

'''source''': valgrind

'''binary''': valgrind

== Usage Examples ==

See the debugging guide <ref name="dbg-guide">[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide|Maemo debugging guide]]</ref> for usage examples.

== Links ==

[valgrind man page](/development/documentation/man_pages/valgrind.html)

[http://valgrind.org/](http://valgrind.org/)
 
[Valgrind tool-suite](http://valgrind.org/info/tools.html)

[Memcheck memory checker](http://valgrind.org/docs/manual/mc-manual.html)

[Massif heap-profiler](http://valgrind.org/docs/manual/ms-manual.html)

[Callgrind profiler](http://valgrind.org/docs/manual/cl-manual.html)

[Helgrind data-race tracker](http://valgrind.org/docs/manual/hg-manual.html)

== See Also ==

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Devtools (edit)

Retrieved from "http://wiki.maemo.org/Documentation/devtools/maemo5/valgrind"

Personal tools

Navigation

Views

Editing Documentation/devtools/maemo5/valgrind

@@ Line 1: / Line 1: @@
-{{Devtools}}
 == Description ==
@@ Line 18: / Line 15: @@
 * ''Cachegrind'': Performance profiling which can be started and stopped at any moment and the results can be sorted according to instructions, cache hits etc.
-* ''Callgrind'': Like Cachegrind, but stores also callgraph information (but can show only instruction counts). Works very well with the Kcachegrind UI.
+* ''Callgrind'': Like Cachegrind, but stores also callgraph information (but can show only instruction counts). Works very well with the Kcachegrind UI.<ref name="kcachegrindui">[http://kcachegrind.sourceforge.net/cgi-bin/show.cgi KCacheGrind]</ref>
 * ''Helgrind'': Detects race conditions when (p)threaded programs access global data
@@ Line 32: / Line 29: @@
 '''binary''': valgrind
+== Usage Examples ==
-== External links ==
+See the debugging guide <ref name="dbg-guide">[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide|Maemo debugging guide]]</ref> for usage examples.
-http://valgrind.org/
+== Links ==
-http://valgrind.org/info/tools.html
-http://valgrind.org/docs/manual/mc-manual.html
+[valgrind man page](/development/documentation/man_pages/valgrind.html)
+[http://valgrind.org/](http://valgrind.org/)
+[Valgrind tool-suite](http://valgrind.org/info/tools.html)
-http://valgrind.org/docs/manual/ms-manual.html
+[Memcheck memory checker](http://valgrind.org/docs/manual/mc-manual.html)
-http://valgrind.org/docs/manual/cl-manual.html
+[Massif heap-profiler](http://valgrind.org/docs/manual/ms-manual.html)
-http://valgrind.org/docs/manual/hg-manual.html
+[Callgrind profiler](http://valgrind.org/docs/manual/cl-manual.html)
-== See also ==
+[Helgrind data-race tracker](http://valgrind.org/docs/manual/hg-manual.html)
-[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger|Maemo debugging guide]]
+== See Also ==
-[[Category:Fremantle]]
+<references/>