https://bugs.kde.org/show_bug.cgi?id=40
Gabriel Ravier changed:
What|Removed |Added
CC||gabrav...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=40
--- Comment #5 from Julian Seward ---
This bug has been reported 5 times in the past year, as bug numbers 393351,
40, 414944, 411303 and 414053. I would like to fix it. I tried the
steps-to-reproduce shown in bugs 393351 and 414053, but without
https://bugs.kde.org/show_bug.cgi?id=40
Tom Hughes changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=40
--- Comment #3 from Andras Szabo ---
Here is the cpuinfo of the build host:
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):80
On-line CPU(s) list: 0-79
Thread(s) per
https://bugs.kde.org/show_bug.cgi?id=40
--- Comment #2 from Tom Hughes ---
The latest (May 2019) edition seems to agree.
Did you compile this yourself, and if you did what architecture did you target
exactly?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=40
--- Comment #1 from Tom Hughes ---
In 32 bit mode 0x62 would be BOUND which would win some sort of obscurity
contest, but in 64 bit mode it doesn't appear to be valid and as far as I can
see it hasn't been replaced by anything else, at least in the
https://bugs.kde.org/show_bug.cgi?id=40
Tom Hughes changed:
What|Removed |Added
Summary|Valgrind causes SIGILL due |vex amd64->IR: unhandled
|to
