On 23 January 2011 09:03, wylda@volny.cz wrote:
Is that somehow useful?
Are there any calls in between? It may just be an application bug.
No, it's complete and taken with WINEDEBUG=+all.
Is there any way to verify such heap corruption on real windows?
Not easily, I think. There are certainly tools like Valgrind for Windows, but I'm not sure if there are any free ones. If there's no Wine code being executed between the allocation and the free it seems unlikely to me that it's a problem in Wine though.