2 Replies to “Valgrind validated”

1. I am not sure for FreeBSD 4.x, but in FreeBSD 5.x you can use /etc/malloc.conf -> AJ instead to debug the memory. It does work great, but I don’t know how it compares with Valgrind. Linux doesn’t has the memory debug, so it will need Valgrind to help debug the things.

2. Valgrind catches things like reading uninitialized variables, too. That’s impossible with malloc.conf ;-) But malloc.conf doesn’t have such a big impact on performance

Comments are closed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)

URL/Permalink of your article