[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-20 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #15 from Austin English --- (In reply to Julian Seward from comment #14) > Landed, c470e0c23c6c79deec943cb6a111b572fc86dbba. Thanks for the quick fix! -- You are receiving this mail because: You are watching all

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386425 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #13 from Austin English --- Created attachment 108909 --> https://bugs.kde.org/attachment.cgi?id=108909=edit output with patch -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #12 from Austin English --- Created attachment 108908 --> https://bugs.kde.org/attachment.cgi?id=108908=edit output without patch -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #11 from Austin English --- (In reply to Julian Seward from comment #10) > Created attachment 108896 [details] > TPIDRURW support for 32-bit arm > > This runs the test program shown in comment 6, correctly, both

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-16 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #10 from Julian Seward --- Created attachment 108896 --> https://bugs.kde.org/attachment.cgi?id=108896=edit TPIDRURW support for 32-bit arm This runs the test program shown in comment 6, correctly, both for Thumb and ARM

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-14 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #9 from Peter Maydell --- Yes, I just mean that each thread sees its own copy with the value it last wrote. On exec() a fresh process image starts out with a zero value. On fork() or clone() a new thread or process

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-14 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #8 from Julian Seward --- (In reply to Peter Maydell from comment #5) > [..] its contents are context-switched when threads are context-switched. [..] Peter, do you mean by that that its contents are preserved across

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-13 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #7 from Austin English --- Re arm/thumb: so you said it's arm encoding. I noticed that configure.ac requires thumb? Do both get used? yes, most of wine should be arm what's thumb used for? Windows Apps are

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-13 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #6 from Austin English --- (In reply to Julian Seward from comment #4) > (In reply to Julian Seward from comment #3) > > IIUC, TPIDRURW is a 32 bit register that can be both read and > > written from user space.

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-13 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=386425 Peter Maydell changed: What|Removed |Added CC|

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-12 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #4 from Julian Seward --- (In reply to Julian Seward from comment #3) > IIUC, TPIDRURW is a 32 bit register that can be both read and > written from user space. Yes? Does it require any special handling? To clarify ..

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-12 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #3 from Julian Seward --- Austin, is this an ARM- or Thumb- encoding that fails? Can you show the part of the message that precedes the SIGILL, that is, whatever the ARM/Thumb front end prints out? IIUC, TPIDRURW is a 32

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-01 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #2 from Austin English --- Forgot to include, some background on why we're doing that: https://patchwork.kernel.org/patch/2536641/ -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

2017-11-01 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=386425 --- Comment #1 from Austin English --- (stretch)austin@localhost:~/src/valgrind$ uname -a Linux localhost 3.14.0 #1 SMP PREEMPT Wed Oct 25 21:59:24 PDT 2017 armv7l GNU/Linux (stretch)austin@localhost:~/src/valgrind$