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:
-
Dec 5, 2009, 1:29:24 AM (14 years ago)
- Author:
-
hamiltont
- Comment:
-
minor change
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v1
|
v2
|
|
| 1 | 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! |
| 2 | | |
| 3 | | $export PURPLE_LEAKCHECK_HELP=1 |
| 4 | | $export G_SLICE=always-malloc |
| | 2 | [[BR]] |
| | 3 | [[BR]] |
| | 4 | $export PURPLE_LEAKCHECK_HELP=1[[BR]] |
| | 5 | $export G_SLICE=always-malloc[[BR]] |
| 5 | 6 | $valgrind --tool=memcheck --leak-check=yes --leak-resolution=high --num-callers=20 --trace-children=no --track-fds=yes pidgin |
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!
