On Dec 20, 2007 10:47 AM, Tom Hughes <[EMAIL PROTECTED]> wrote:
> I have recently been working on trying to get valgrind and wine to
> work together

Yay!

> I've read Dan Kegel's information at
> http://wiki.winehq.org/Wine_and_Valgrind and looked at his patch but
> it doesn't address the issue I'm having.

It's not my patch - I'm just providing a rediff of a rollup of a
patch from Eric Pouech and maybe Adam Gundy; the
origins are lost in the sands of time :-)

> The problem of course is that under valgrind the wine preloader fails
> to map that low address space (if for no other reason than that
> valgrind is in the middle of it!) and so when it starts loading wine
> there is a risk that some of will wind up in the place where wine will
> want to load the windows executable.
>
> In my case the problem was actually libwine.so, which the prelinker
> had  chosen to load in exactly the wrong place ;-)

I've noticed warnings about the wine preloader not getting
its way, but so far they haven't annoyed me too much,
I must be lucky.  (I'm also not really too worried about whether
valgrind works on individual apps yet, as I'm still mostly just
running it on the entire wine test suite, and am happy when
I get meaningful results for 90% of that.)
- Dan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers

Reply via email to