 |
 |
Valgrind works on the per-malloc level; it will catch a write past a malloc boundary, even if on the same page (It's the reason it is 30x slower!).
Valgrind won't catch (a) stack issues or (b) improper writes within a single malloc (if you, for example, have two objects sitting inside one malloc allocation).
Can you describe further the issue you saw? I could probably guess whether it would apply here.
—
Reply to this email directly or view it on GitHub.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1