Wine and Valgrind / handling SIGILL

[Austin English]

Howdy all,

Several months ago, a patch from Sebastian:
commit 44fbc018eda12bdee5c2c1e2e40dbdc6a81b27fd
Author: Sebastian Lackner <sebastian at fds-team.de>
Date:   Thu Feb 12 11:09:34 2015 +0100

    winebuild: Do not access memory below ESP when restoring thread
contexts.

    Based on a patch by John Reiser.

for https://bugs.winehq.org/show_bug.cgi?id=14367

Caused problems for running Wine under Valgrind:
https://bugs.kde.org/show_bug.cgi?id=344139

There are patches floating around for both Wine and Valgrind (see
previous link), but from what I've seen so far, both projects aren't a
fan of the current patches.

Given that Wine developers like using Valgrind to check for problems,
and I know Julian would like to use Wine with Valgrind, I feel like some
solution to this problem can be found. Since my efforts at trying to run
messages between the two projects hasn't solved it yet, I figured an
email thread would work better ;).

-- 
-Austin
GPG: 14FB D7EA A041 937B

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 866 bytes
Desc: OpenPGP digital signature
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20161205/4e652038/attachment.sig>