Running valgrind with Wine

[Saulius Krasuckas]

On Sun, 5 Sep 2004, Mike McCormack wrote:
> Saulius Krasuckas wrote:
> > Hm, still, for me valgrind doesn't work:
> > 
> > [s2 at katleriai wine]$ valgrind --tool=memcheck wine-pthread notepad.exe
> > Executable range 0x77f00000-0x77f02370 is outside the
> > acceptable range (nil)-0x52c00000
> > valgrind: do_exec(/usr/local/bin/wine-pthread) failed: Cannot allocate memory
> > [s2 at katleriai wine]$ 
> 
> Which version of valgrind... some of them work and some don't.  I think 
> I'm still using one built with Adam Gundy's patches.

Nice idea.  Yesterday I have compiled the latest one.

> bash-2.05b$ valgrind --version
> valgrind-20031012

[s2 at katleriai wine]$ valgrind --version
valgrind-2.2.0

> I'm also using wine-kthread, but that shouldn't make a difference.

Have installed the same version as yours.

[s2 at katleriai wine]$ valgrind --version
valgrind-20031012
[s2 at katleriai wine]$ valgrind wine-pthread --version
==27403== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==27403== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward.
==27403== Using valgrind-20031012, a program supervision framework for x86-linux.
==27403== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward.
==27403== Estimated CPU clock rate is 856 MHz
==27403== For more details, rerun with: -v
==27403== 
==27403== Warning: set address range perms: large range 1073610752, a 1, v 1
Killed
[s2 at katleriai wine]$ 


Wow, it made some LAAAAAAG on my box.

I think i eats all of my RAM and then gets killed by the kernel.  I guess
valgrind wants ~1GB of RAM (or RAM+Swap) while I have only 256+300 MBs.

Bad luck.