http://bugs.winehq.org/show_bug.cgi?id=32169
--- Comment #6 from Sn3akyP3t3 WineHQBugzilla.sn3akyp3t3@spamgourmet.com 2013-11-03 22:14:02 CST --- I'm sorry I posted to bug id 32169, I had thought the bug I created was numbered 32170 so not sure whats going on there.
I'm available to provide testing if someone could kindly let me know how to apply the patch.
Also, I posted this in the other 32170 bug id and thought it wasn't answered.
From the developer of PowerGREP, Jan Goyvaerts,
"If I correctly interpret the meaning of "stub" in the the dump you posted at http://bugs.winehq.org/show_bug.cgi?id=32170 then it seems that the debug build crashes because WINE does ot implement the GetLogicalProcessorInformation API call.
PowerGREP itself (or any of our other products) never calls GetLogicalProcessorInformation. But the 3rd party component that we use to add the bug logging system to our debug builds does call GetLogicalProcessorInformation.
If my observations are correct, then you won't be able to use any of our (64-bit) debug builds until (64-bit) WINE implements GetLogicalProcessorInformation. You also won't be able to run any other (64-bit) applications that use Eurekalog for bug logging. This is a fairly popular component among Delphi developers. We only use it in our debug builds, but some developers like to include it in their release builds too. I can build a dummy application that includes the bug logging system as we use it if that would be helpful to the WINE developers."
Would there be any need for a bug logging system for testing with WINE? I'm not sure all of what that entails.