Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Apr 18, 2010, 7:55:02 PM (14 years ago)
- Author:
-
darkrain42
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v6
|
v7
|
|
| 1 | | This page is intended to help developers understand how to best memory check their plugin using the popular tool valgrind. It is currently bare bones, and will be updated soon! |
| | 1 | Valgrind is a debugg |
| | 2 | |
| | 3 | This page is intended to help developers/users understand how to best memory check their plugin using the popular tool valgrind. It is currently bare bones, and will be updated soon! |
| 2 | 4 | {{{ |
| 3 | 5 | $ export PURPLE_LEAKCHECK_HELP=1 |
| 4 | 6 | $ export G_SLICE=always-malloc |
| 5 | | $ valgrind --tool=memcheck --leak-check=yes --leak-resolution=high --num-callers=20 --trace-children=no --child-silent-after-fork=yes --track-fds=yes pidgin -d |
| | 7 | $ valgrind --tool=memcheck --leak-check=yes --leak-resolution=high --num-callers=20 --trace-children=no --child-silent-after-fork=yes --track-fds=yes pidgin -d >valgrind.log 2>&1 |
| 6 | 8 | }}} |
| 7 | 9 | |
| 8 | 10 | If valgrind supports it, add `--track-origins=yes` to the above. It makes diagnosing issues ridiculously easier. |
| | 11 | |
| | 12 | I also enjoy using ` | tee valgrind.log` instead of `>valgrind.log 2>&` (visual feedback of what valgrind is doing) |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!
