Re: Running valgrind with Wine

2004-09-05 Thread Boaz Harrosh
Mike Hearn wrote: While we're technically not API stable yet, it's painfully obvious that 1.0 is still a long way away. Stability is a policy rather than a target, so we've got to start at some point I totally agree but that should not stop you from doing things Like: +wine_init_ex( arg

Re: Running valgrind with Wine

2004-09-05 Thread Mike McCormack
Saulius Krasuckas wrote: Possibly, it works. That just I suck: the patch was not applied. :-/ Well, so long as it's working :) Instead I am having trouble compiling the libs/wine dir: loader.c:524: conflicting types for `wine_init' ../../include/wine/library.h:56: previous declaration of `wine_ini

Re: Running valgrind with Wine

2004-09-05 Thread Saulius Krasuckas
On Sun, 5 Sep 2004, Mike McCormack wrote: > Saulius Krasuckas wrote: > > 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. > > That's exactly the problem I was trying to fix... it's eating 1Gb o

Re: Running valgrind with Wine

2004-09-05 Thread Mike McCormack
Saulius Krasuckas wrote: Wow, it made some LAAG 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. That's exactly the problem I was trying to fix... it's eating 1Gb of RAM because Wine is

Re: Running valgrind with Wine

2004-09-05 Thread Saulius Krasuckas
On Sun, 5 Sep 2004, Mike McCormack wrote: > Saulius Krasuckas wrote: > > Hm, still, for me valgrind doesn't work: > > > > [EMAIL PROTECTED] wine]$ valgrind --tool=memcheck wine-pthread notepad.exe > > Executable range 0x77f0-0x77f02370 is outside the > > acceptable range (nil)-0x52c0 > > v

Re: Running valgrind with Wine

2004-09-05 Thread Mike McCormack
Saulius Krasuckas wrote: Hm, still, for me valgrind doesn't work: [EMAIL PROTECTED] wine]$ valgrind --tool=memcheck wine-pthread notepad.exe Executable range 0x77f0-0x77f02370 is outside the acceptable range (nil)-0x52c0 valgrind: do_exec(/usr/local/bin/wine-pthread) failed: Cannot allocat

Re: Running valgrind with Wine

2004-09-05 Thread Saulius Krasuckas
On Sat, Sep 04 2004, Mike McCormack wrote: > Valgrind stopped working with Wine a while back due to the way Wine > reserves memory above address 0x8000. > > The following patch allows valgrind to work with wine again. You need to > start wine-pthread or wine-kthread instead of starting the win

Re: Running valgrind with Wine

2004-09-05 Thread Mike Hearn
On Sun, 05 Sep 2004 12:55:33 +0900, Mike McCormack wrote: > -wine_init( argc, argv, error, sizeof(error) ); > +wine_init( argc, argv, error, sizeof(error), reserve ); It's worth noting that any change to this functions prototype breaks the Ardour/Wine VST plugin bridge. Last time this issu