Ulrich Weigand wrote:
On the other hand, maybe it would now be possible to implement Wine threads on top of regular pthreads; at least some of the inhibitors should be gone now, e.g. you can have thread stacks at arbitrary locations and sizes, and there is no master thread any more ... Unfortunately I don't quite remember the full list of problems we had with pthreads ;-/
It occurs to me that implementing Wine threads on top of pthreads would probably get rid of a few of the problems keeping us from running Wine under Valgrind. Short of getting the Stanford Checker guys interested in the Wine source tree, I can't think of an cooler way to look for stupid memory bugs in Wine... - Dan
Can Valgrind run GL programs (except NVidia binaries-linked ;)) ?
It occurs to me that implementing Wine threads on top of pthreads would probably get rid of a few of the problems keeping us from running Wine under Valgrind. Short of getting the Stanford Checker guys interested in the Wine source tree, I can't think of an cooler way to look for stupid memory bugs in Wine...
- Dan
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Sylvain Petreolle wrote:
It occurs to me that implementing Wine threads on top of pthreads would probably get rid of a few of the problems keeping us from running Wine under Valgrind. Short of getting the Stanford Checker guys interested in the Wine source tree, I can't think of an cooler way to look for stupid memory bugs in Wine...
Can Valgrind run GL programs (except NVidia binaries-linked ;)) ?
Yes. See http://developer.kde.org/~sewardj/
-
Dan Kegel -
Sylvain Petreolle