in reply to Re: Mark-and-sweep-like mechanism to verify refcount integrity
in thread Mark-and-sweep-like mechanism to verify refcount integrity

While valgrind is an excellent tools to check whether perl itself has any memory related problems, it won't help at all for debugging Perl programs. valgrind sits between perl and the OS (roughly speaking) and checks memory access with respect to malloc()ed and free()d memory. valgrind doesn't know the difference between an SV and a hole in the ground.
  • Comment on Re^2: Mark-and-sweep-like mechanism to verify refcount integrity