Re: [Valgrind-users] Re: Valgrind and Wine

[b12 a.k.a. F. B. <b12...@ya...>]

Adam Gundy wrote:

>no, you shouldn't need trace-children. the wine-pthread process contains the
>Windows executable, rather than running it as a sub-process.
>
>also, helgrind won't work. if it does, it won't be useful as Tom says.
>
>make sure you have the PDB files for the program you're trying to debug..
>without them, valgrind-WINE can't tell you where the errors are.
>
>also, make sure you're using the WINE supplied MSVCRTD.DLL instead of one
>copied from Windows, otherwise valgrind won't report heap problems... this
>implies that you have to be working with a Debug build of your program.
>
>finally, I do have a tarball based on valgrind-2.1.0 which I can send, or
>get Jeremy to put on the website. it's not been very heavily tested though,
>so YMMV.
>
>
>Seeya,
> Adam
>  
>
Thank you for all these clarifications (is this an English word?)

Looks like I will not be able to use Valgrind / Wine on my windows 
application.
First, helgrind was the tool I wanted to play with. And I don't have PDB 
files for my program. Moreover it does not use MSVCRTD.DLL (It's not  
built with  MS tools).
I think it will be faster to port my program to linux to use valgrind on it.

However I would be interested to test your valgrind-2.1.0 based tarball.
You can send it to me by mail if you please. But if you can have it 
published on the web site I think it will be of some interest for other 
people.

Thanks again,
Fabrice