Documentation/devtools/maemo5/valgrind - Revision history

imported_>amigadave: devtools template

2010-03-11T15:24:53Z

devtools template

← Older revision		Revision as of 15:24, 11 March 2010
Line 1:		Line 1:
			{{Devtools}}


	== Description ==		== Description ==

Line 48:		Line 51:
	[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger\|Maemo debugging guide]]		[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger\|Maemo debugging guide]]

	~~[[Category:Devtools]]~~
	[[Category:Fremantle]]		[[Category:Fremantle]]

imported_>amigadave: Category:Devtools and Category:Fremantle

2010-02-12T11:49:17Z

Category:Devtools and Category:Fremantle

← Older revision		Revision as of 11:49, 12 February 2010
Line 47:		Line 47:

	[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger\|Maemo debugging guide]]		[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger\|Maemo debugging guide]]

			[[Category:Devtools]]
			[[Category:Fremantle]]

imported_>amigadave: partially wikify

2010-01-28T13:52:15Z

partially wikify

← Older revision		Revision as of 13:52, 28 January 2010
Line 15:		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.		* ''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>~~		* ''Callgrind'': Like Cachegrind, but stores also callgraph information (but can show only instruction counts). Works very well with the Kcachegrind UI.

	* ''Helgrind'': Detects race conditions when (p)threaded programs access global data		* ''Helgrind'': Detects race conditions when (p)threaded programs access global data
Line 29:		Line 29:
	'''binary''': 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.~~		== External links ==

	== ~~Links~~ ==

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

	http://valgrind.org/		http://valgrind.org/
Line 49:		Line 44:
	http://valgrind.org/docs/manual/hg-manual.html		http://valgrind.org/docs/manual/hg-manual.html

	== See ~~Also~~ ==		== See also ==

	~~<references~~/>		[[Documentation/Maemo_5_Developer_Guide/Kernel_and_Debugging_Guide/Maemo_Debugging_Guide#Valgrind_Debugger\|Maemo debugging guide]]

imported_>kaltsi at 07:42, 7 October 2009

2009-10-07T07:42:43Z

← Older revision		Revision as of 07:42, 7 October 2009
Line 37:		Line 37:
	[valgrind man page](/development/documentation/man_pages/valgrind.html)		[valgrind man page](/development/documentation/man_pages/valgrind.html)

	[http://valgrind.org/~~](http://valgrind.org/)~~		http://valgrind.org/

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

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

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

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

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

	== See Also ==		== See Also ==

	<references/>		<references/>

imported_>kaltsi at 07:39, 7 October 2009

2009-10-07T07:39:15Z

← Older revision		Revision as of 07:39, 7 October 2009
Line 31:		Line 31:
	== Usage Examples ==		== Usage Examples ==

	See the [~~maemo~~ debugging guide][] for 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 ==		== Links ==
Line 48:		Line 48:

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

	~~[maemo debugging guide][]~~

	~~[maemo debugging guide]: /development/documentation/how-tos/4-x/maemo_debugging_guide.html~~

	== See Also ==		== See Also ==

	<references/>		<references/>

imported_>kaltsi: New page: == 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...

2009-10-01T11:13:43Z

New page: == 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...

New page

== 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 [maemo debugging guide][] 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)

[maemo debugging guide][]

[maemo debugging guide]: /development/documentation/how-tos/4-x/maemo_debugging_guide.html

== See Also ==

<references/>