I've been thinking a bit about your Wine patches, and even looked at
http://www.winehq.com to see if anyone mentioned anything more about running
Wine on V. It would be nice to see a whole bunch of bug fixes to Wine
committed as a result.
I think it will be a significant period of time before your changes
can get integrated into the head. One reason is that there are a
various plans in discussion regarding other changes to the head,
(SSE, NPTL, elf loaders, more modularity) which will soak up our
time for a while. Also, JeremyF is away for a month, and he seems
to have the best understanding of how your changes interact with
JeffD's/his changes for UML and how to reconcile the two.
Just in case it isn't clear, I think it's excellent that you've
made V work with Wine. It's unfortunate that the stuff you've
had to change is the most awkward part of V -- the "environment
simulation" -- signals, threads, etc -- which is why it's hard
to figure out the best way to merge it.
So, my suggestion is that for the time being you make
your patch available as a patch against the current stable version,
1.9.5. (The 1.0.X series is now officially dead). Although not ideal,
it makes your stuff available right now to Wine hackers. I hope that
1.9.X is not going to change very much at all, since it is a stable
branch, and so you will have little or zero hassle tracking the
If you want, I can put suitable links on the valgrind web page
(http://developer.kde.org/~sewardj) to your patch distributing
page(s), saying "You can debug Wine with a patched valgrind;
see here (link) for a patch against 1.9.5".
(Somewhat off-topic, but ...) Is there a list anywhere of the bugs you
found in Wine? I'd be interested to see ...
Get latest updates about Open Source Projects, Conferences and News.