https://bugs.winehq.org/show_bug.cgi?id=45845
--- Comment #15 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Zebediah Figura from comment #14)
While this particular regression was not caused by returning wrong value due an exception, it's still worth IMO to add the tests to the listed above APIs to check their behaviour.
Zebediah, since that's your patch are you planning to investigate this?
I'm not sure how to force any of those APIs to cause a page fault on Windows. Do you have any ideas?
Setting a break point on an rpcrt4 API that MSI uses for calling to the remote side seems a workable solution. A starting point would be to figure out first which one to exploit for this purpose.