Editing Documentation/Maemo 5 Developer Guide/Kernel and Debugging Guide/Maemo Debugging Guide
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
Warning: This page is 60 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.
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.
Latest revision | Your text | ||
Line 1,007: | Line 1,007: | ||
* '''<code>--leak-check=yes</code>:''' With this option, Valgrind checks the code for potential memory leaks. | * '''<code>--leak-check=yes</code>:''' With this option, Valgrind checks the code for potential memory leaks. | ||
- | * '''<code>--show-reachable=yes</code>:''' This option creates a stack trace of the creation of the reachable but unfreed memory when the program exits. | + | * '''<code>--show-reachable=yes</code>:'''This option creates a stack trace of the creation of the reachable but unfreed memory when the program exits. |
* '''<code>--num-callers=20</code>:''' With this option, the number of function call levels that Valgrind displays can be changed. The default value is 12. Giving higher number takes a bit more memory. It is advisable to tune this option, because for example the gtk callstack can consist of more than 100 items. | * '''<code>--num-callers=20</code>:''' With this option, the number of function call levels that Valgrind displays can be changed. The default value is 12. Giving higher number takes a bit more memory. It is advisable to tune this option, because for example the gtk callstack can consist of more than 100 items. |
Learn more about Contributing to the wiki.