[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-09 Thread Tiago Martinho 
https://bugs.kde.org/show_bug.cgi?id=476662

--- Comment #5 from Tiago Martinho  ---
(In reply to Paul Floyd from comment #4)
> What is the library? Is it public?

Unfortunately it's not a public library and I do not have access to the source
code.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-08 Thread Paul Floyd 
https://bugs.kde.org/show_bug.cgi?id=476662

Paul Floyd  changed:

   What|Removed |Added

 CC||pjfl...@wanadoo.fr

--- Comment #4 from Paul Floyd  ---
What is the library? Is it public?

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-08 Thread Tiago Martinho 
https://bugs.kde.org/show_bug.cgi?id=476662

--- Comment #3 from Tiago Martinho  ---
(In reply to Mark Wielaard from comment #2)
> Is this only an issue with this hand assembly?
> It would be interesting to see real code that uses this.

Hi! I got this code from a library I depend on. Unfortunately I do not have
access to the source code, but the disassembled code does have this
instruction. I tried to give an example so that the issue could be reproduced.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-08 Thread Mark Wielaard 
https://bugs.kde.org/show_bug.cgi?id=476662

--- Comment #2 from Mark Wielaard  ---
Is this only an issue with this hand assembly?
It would be interesting to see real code that uses this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-07 Thread Mark Wielaard 
https://bugs.kde.org/show_bug.cgi?id=476662

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@klomp.org
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Mark Wielaard  ---
This looks like the size == 2 issue in VEX/priv/guest_amd64_toIR.c
(dis_ESC_NONE):

   case 0x9D: /* POPF */
  /* Note.  There is no encoding for a 32-bit popf in 64-bit mode.
 So sz==4 actually means sz==8. */
  if (haveF2orF3(pfx)) goto decode_failure;
  vassert(sz == 2 || sz == 4 || sz == 8);
  if (sz == 4) sz = 8;
  if (sz != 8) goto decode_failure; // until we know a sz==2 test case
exists

So here is an example where sz == 2. Question is if it is a valid example.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476662] vex amd64->IR: unhandled instruction bytes: 0x66 0x9D (popf)

2023-11-07 Thread Tom Hughes 
https://bugs.kde.org/show_bug.cgi?id=476662

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu
Summary|Popfw causes crash  |vex amd64->IR: unhandled
   ||instruction bytes: 0x66
   ||0x9D (popf)

-- 
You are receiving this mail because:
You are watching all bug changes.