http://bugs.winehq.org/show_bug.cgi?id=22580
--- Comment #58 from joakim.tjernlund@transmode.se 2010-05-18 01:56:51 --- (In reply to comment #57)
(In reply to comment #56)
(In reply to comment #55)
(In reply to comment #54)
In your small world it is, but what if I found an app that did the same? Is this app also invalid? The newer Windows you refer to is a minority of all Windows systems.
And what if you won't ever found it? Workaround will be useless in this case.
Feel free to reopen if you really found it.
That was not an answer. If you really think that this native crypt32 dll is then only app that uses this feature, why don't you confirm it by working through the open 100% CPU bugs and actually verify that this is the case? And before you ask, it is not my job to do that for you.
Developer time is spread thin enough as is. If you want that patch in wine, you need to find an application using that behavior, and you haven't done so.
Your effort would be better spent getting your testcase into wine, and/or testing other 100% cpu bugs to confirm your theory.
The testcase is worthless as it would just report what we already know. Asking me to find yet another app that has this particular use is too much. Consider that you don't even want to check your 100% CPU bugs wrt. to this problem.
Here is a hint for you though that might be acceptable. Add a trace for tmo == 0 && !executeOnce. Then you will quickly see/find potential problem apps. I am not doing that for you though.