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 58 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 71: | Line 71: | ||
=== Setting up Environment === | === Setting up Environment === | ||
- | Both the Internet Tablet device, described in section [[ | + | Both the Internet Tablet device, described in section [[../../Development Environment/Maemo PC Connectivity|Maemo PC Connectivity]], and the Scratchbox environment, described in section [[../../Development Environment/Maemo SDK|Maemo SDK]], need to be set up. |
=== Preparing Scratchbox Environment for Debugging === | === Preparing Scratchbox Environment for Debugging === | ||
Line 526: | Line 526: | ||
</pre> | </pre> | ||
- | In this example, the standard | + | In this example, the standard export DEB_BUILD_OPTIONS=debug,nostrip environment variable is used, but there might be source packages that do not support these debug,nostrip options. In that case, one must make sure that the source is compiled with <code>-g</code> flag (usually this option can be added to the <code>CFLAGS</code> variable in the <code>debian/rules</code> file), and that the produced binaries will not be stripped. In the long run, it is better to modify the source package to generate a separate debug symbol (<code>-dbg</code>) package. This requires modifying both the <code>debian/rules</code> and <code>debian/control</code> files. In fact, maemopad already builds a separate debug package, but this example makes no use of it to demonstrate the simpler case. |
Line 719: | Line 719: | ||
Because the breakpoint is now cleared, you can use the application normally under <code>Xephyr</code>. | Because the breakpoint is now cleared, you can use the application normally under <code>Xephyr</code>. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== Debugging Hildon Desktop Plug-ins == | == Debugging Hildon Desktop Plug-ins == | ||
Line 1,064: | Line 1,058: | ||
Valgrind also tells the lines in the code where these allocations that are not freed are performed. In this example, the lines in question are 48 and 26. | Valgrind also tells the lines in the code where these allocations that are not freed are performed. In this example, the lines in question are 48 and 26. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
=== Official Valgrind Manual === | === Official Valgrind Manual === |
Learn more about Contributing to the wiki.