At 08:18 PM 12/22/2004 -0800, Tom Hughes wrote:
>> That is the way I tried it. Here is the exact command line I used:
>> valgrind --tool=helgrind --trace-children=yes wine-pthread test.exe
>> Note that if I don't use the --trace-children=yes option, it's working
>> fine. But I don't thing that without this option valgrind debugs
>> something else than wine itself.
>> Or maybe I'm wrong with this?
>We only ever used memcheck I think. I doubt helgrind will be very
>useful anyway as it won't be able to see the Windows threading calls
>but will instead be monitoring the pthread calls that wine itself
>makes and there is little correspondence between the two.
>As to --trace-children, you shouldn't need that as far as I can
>recall, but I might be wrong.
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,
Real Programmers don't comment their code. If it was hard to write,
it should be hard to read, and even harder to modify.
These are all my own opinions.