Re: Fixing NTQueryVirtualMemory once and for all (Was: Borland C++ 5.5 fails on Link, any ideas?)

[Alexandre Julliard]

Troy Rollo  writes:
> So there's really two issues:
> - How should we deal with the 0x80000000 boundary anomaly?

By allocating something there.
> - Should we attempt to deal with the fact that NtQueryVirtualMemory
>  doesn't report memory used by native executables and libraries?

Only if we find an actual app that depends on that.