Sam Varshavchik wrote:
Philip Prindeville writes:
> The large address space is full of potential...
>
> I'd like to see someone do the following:
>
> * a 64-bit (or 48-bit) address space implementation of a GPL memory leak
> finder like Rational's "Purify".
valgrind now supports amd64.
Does that mean that it supports sparse allocation with "hole"
interlacing between
individual chunks?
Or just that it was recompiled with -m64?
-Philip