valgrind and wine
aric at codeweavers.com
Mon Dec 2 10:14:28 CST 2002
I have actually worked a little with Julian Steward on this problem
just before 1.1.0 I actually have a build of valgrind here on my laptop
with works with very simple wine applications. I remember there was one
hack i had to do to the valgrind source to disable some of its sanity
I could not get valgrind to work with more advanced wine programs
because i kept getting
trace:seh:EXC_RtlRaiseException code=eedfade flags=1 addr=0x402e1a30
if you want to work with valgrind i will did up how i turned off the
sanity checking with 1.1.0 and see if you can get it working.
Lionel Ulmer wrote:
>>==6476== Valgrind detected that your program requires
>>==6476== the following unimplemented functionality:
>>==6476== modify_ldt(): I (JRS) haven't investigated this yet; sorry.
>>==6476== This may be because the functionality is hard to implement,
>>==6476== or because no reasonable program would behave this way,
>>==6476== or because nobody has yet needed it. In any case, let me know
>>==6476== (jseward at acm.org) and/or try to work around the problem, if you can.
> Which version of Valgrind is this ? According to the web page, 1.1.0 should
> support this system call : 'Specifically, valgrind can now deal with x86
> segment registers, segment override prefixes and the modify_ldt system
> But well, for it to really be useful, we would need then also to override in
> Valgrind (or in Wine) all the Threading and Heap functions.
More information about the wine-devel