zirias@
Developer
Explaining the usecase first: I very rarely need a memory debugger. But WHEN I do, it's typically for the reason of having UB somewhere in my code that I just can't find. This often results in situations where the "debug build" seems to work perfectly, but the "release build" crashes or misbehaves somewhere, often not reproducible. A memory debugger often helps by finding things like:
For things like that, I used to use devel/valgrind (and DrMemory on Windows). Valgrind never worked perfectly on FreeBSD, I now don't remember what exactly was broken, but was still useful sometimes. Now, it is marked BROKEN:
Is there any tool with the features described above I could use on FreeBSD instead?
- off-by-one errors (out of bounds accesses)
- use after free errors
- use of uninitialized memory
For things like that, I used to use devel/valgrind (and DrMemory on Windows). Valgrind never worked perfectly on FreeBSD, I now don't remember what exactly was broken, but was still useful sometimes. Now, it is marked BROKEN:
fails at runtime: valgrind: mmap(0x200000, 45056) failed in UME with error 22 (Invalid argument)
.Is there any tool with the features described above I could use on FreeBSD instead?