[Valgrind-developers] Wine and Valgrind / handling SIGILL

Austin English austinenglish at gmail.com
Fri Jan 20 13:10:32 CST 2017

On Fri, Jan 20, 2017 at 4:15 AM, Julian Seward <jseward at acm.org> wrote:
> On 20/01/17 09:12, Austin English wrote:
>>> I have attached a new series which is hopefully less hacky:
>>> https://bugs.kde.org/show_bug.cgi?id=344139#c3 (*)
>>> https://bugs.kde.org/show_bug.cgi?id=344139#c4
> Landed, r16204, r3299.

Great, thanks!

>> My wine/valgrind branch has one other patch, for
>> https://bugs.winehq.org/show_bug.cgi?id=39097. So I also tried
>> reapplying 4a1629c4117fda9eca63b6f56ea45771dc9734ac, and rerunning
>> dlls/comdlg32/tests/filedlg.c with valgrind, but it still hangs.
> What's the Valgrind patch there?  I can't see any patch attached to
> https://bugs.winehq.org/show_bug.cgi?id=39097.

Sorry if I was unclear, there's not one. It was a wine change that
causes problems for me running under valgrind, but apparently not

GPG: 14FB D7EA A041 937B

More information about the wine-devel mailing list