Bug 241290 - unhandled instruction bytes: 0xF3 0xF 0xBD 0x84
Summary: unhandled instruction bytes: 0xF3 0xF 0xBD 0x84
Status: RESOLVED DUPLICATE of bug 212335
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.6 SVN
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 12:52 UTC by smf.linux
Modified: 2010-06-10 13:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description smf.linux 2010-06-10 12:52:19 UTC
Version:           3.6 SVN (using KDE 1.2) 
OS:                Linux

==17591== Memcheck, a memory error detector
==17591== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==17591== Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright info
==17591== Command: ./aterm
==17591== 
vex x86->IR: unhandled instruction bytes: 0xF3 0xF 0xBD 0x84
==17591== valgrind: Unrecognised instruction at address 0x465980a.
==17591== Your program just tried to execute an instruction that Valgrind
==17591== did not recognise.  There are two possible reasons for this.
==17591== 1. Your program has a bug and erroneously jumped to a non-code
==17591==    location.  If you are running Memcheck and you just saw a
==17591==    warning about a bad jump, it's probably your program's fault.
==17591== 2. The instruction is legitimate but Valgrind doesn't handle it,
==17591==    i.e. it's Valgrind's fault.  If you think this is the case or
==17591==    you are not sure, please let us know and we'll try to fix it.
==17591== Either way, Valgrind will now raise a SIGILL signal which will
==17591== probably kill your program.


Reproducible: Always

Steps to Reproduce:
valgrind <any application>

Actual Results:  
Always fails with the same unhandled instruction error.

This problem has been with this AMD Phenom system since it was put together in Jan 2009 it seems to be independent of Linux Kernel,GCC, BinUtils, GLIBC and Valgrind versions which have been updated periodically since that date (see additional information) same problem every time. The machine is generally stable and other debug tools I use work as expected.

Expected Results:  
N/A

Linux Andromeda 2.6.33.5 #11 SMP Sat May 29 10:04:08 BST 2010 i686 athlon-4 i386 GNU/Linux

vendor_id       : AuthenticAMD
cpu family      : 16
model           : 4
model name      : AMD Phenom(tm) II X4 940 Processor

GNU C Library stable release version 2.11.2, by Roland McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.5.0.
GNU assembler etc. (GNU Binutils) 2.20.1.20100303
Compiled on a Linux 2.6.33 system on 2010-06-01.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
Comment 1 Tom Hughes 2010-06-10 13:21:31 UTC

*** This bug has been marked as a duplicate of bug 212335 ***