https://www.dragonflydigest.com/2004/01/24/valgrind-validated/ A running description of activity related to DragonFly BSD. Sat, 24 Jan 2004 23:50:50 +0000 hourly 1 https://wordpress.org/?v=7.1.3 https://www.dragonflydigest.com/2004/01/24/valgrind-validated/comment-page-1/#comment-103 Sat, 24 Jan 2004 23:50:50 +0000 http://www.shiningsilence.com/dbsdlog/?p=222#comment-103 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

]]> https://www.dragonflydigest.com/2004/01/24/valgrind-validated/comment-page-1/#comment-102 Sat, 24 Jan 2004 23:27:32 +0000 http://www.shiningsilence.com/dbsdlog/?p=222#comment-102 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.

]]>