|
|
|
|
|
by wallstprog
1287 days ago
|
|
It's been a while, but IIRC ASAN catches most/all of the memory-related errors that Purify did. Purify did have a debugger-like GUI that would break on errors, which could be handy. valgrind can also do most of the same checks, but is much slower. On my team we use both |
|