http://bugs.winehq.org/show_bug.cgi?id=11052
--- Comment #6 from Peter Oberndorfer kumbayo84+wine_bugzilla@gmail.com 2008-01-06 12:13:27 --- (In reply to comment #4)
Does that explain any of the warnings at http://kegel.com/wine/valgrind/logs-2008-01-03/vg-crypt32_cert.txt ?
I am not sure but i would say no, since all those errors have main and run_test on the stack
I tried to run valgrind on my minimized testcase, but it did not report any errors regarding crypt32 I need to research more why this error is not reported. I would guess the memory is allocated again and thus also valid again. I will try to create a patch which does not free memory, only make it unaccessible for VG, so it is raises a error when the program is accessing it.
(In reply to comment #5)
I guess I forgot to file a bug for it, but I have essentially the same problem in winmm where it tries to call DriverProc for a video codec that has already been unloaded. FWIW, I sent this patch:
http://winehq.org/pipermail/wine-patches/2007-December/047489.html
Looks like it has not been applied yet, if this is the right way to also solve the crypt32 problem i can create/send a patch for it