[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 301902] vex amd64->IR: unhandled instruction bytes: 0xF 0xB 0xF 0x1F 0x0 0x40 0x38 0xFE
From:       John Reiser <jreiser () bitwagon ! com>
Date:       2012-06-30 21:55:12
Message-ID: bug-301902-17878-EcBeQFtHJz () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=301902

John Reiser <jreiser@bitwagon.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jreiser@bitwagon.com

--- Comment #1 from John Reiser <jreiser@bitwagon.com> ---
The first two bytes 0xF 0xB are 'ud2', which is the official two-byte
"undefined opcode"; all following bytes "0xF 0x1F 0x0 0x40 0x38 0xFE" are not
relevant.  From the point of view of the app, then the real error happened some
time ago; the ud2 is just "I give up".  So, this bug will become a slog to scan
backwards (logically, in the execution history) to find the place where the
real error occurred.

Valgrind should recognize ud2 for what it is, and not confuse itself and the
user.  Handle the instruction bytes 0xF 0xB as "fatal error."

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]