[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [valgrind] [Bug 334157] New: vex amd64->IR: unhandled instruction bytes: 0xF3 0x48 0xF 0xBC 0x16 0x8
From: <bnagaev () gmail ! com>
Date: 2014-04-30 20:30:59
Message-ID: bug-334157-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=334157
Bug ID: 334157
Summary: vex amd64->IR: unhandled instruction bytes: 0xF3 0x48
0xF 0xBC 0x16 0x83 0x7D 0xB8
Classification: Unclassified
Product: valgrind
Version: 3.7.0
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: vex
Assignee: jseward@acm.org
Reporter: bnagaev@gmail.com
vex amd64->IR: unhandled instruction bytes: 0xF3 0x48 0xF 0xBC 0x16 0x83 0x7D
0xB8
==23501== valgrind: Unrecognised instruction at address 0x58b95cd.
==23501== at 0x58B95CD: __printf_fp (printf_fp.c:797)
==23501== by 0x58B7134: vfprintf (vfprintf.c:1648)
==23501== by 0x58D815A: vsprintf (iovsprintf.c:42)
==23501== by 0x58BC8A6: sprintf (sprintf.c:32)
==23501== by 0xABF45C: bool boost::detail::lexical_stream_limited_src<char,
std::char_traits<char>, false>::shl_double<char>(double, char*)
(lexical_cast.hpp:1298)
==23501== by 0xABE949: boost::detail::lexical_stream_limited_src<char,
std::char_traits<char>, false>::operator<<(double) (lexical_cast.hpp:1422)
==23501== by 0xABDD0F: boost::detail::lexical_cast_do_cast<std::string,
double>::lexical_cast_impl(double const&) (lexical_cast.hpp:1921)
==23501== by 0xABD1D1: std::string boost::lexical_cast<std::string,
double>(double const&) (lexical_cast.hpp:2088)
==23501== by 0xB55A65: boost::program_options::typed_value<double,
char>::default_value(double const&) (value_semantic.hpp:198)
...
==23501== Your program just tried to execute an instruction that Valgrind
==23501== did not recognise. There are two possible reasons for this.
==23501== 1. Your program has a bug and erroneously jumped to a non-code
==23501== location. If you are running Memcheck and you just saw a
==23501== warning about a bad jump, it's probably your program's fault.
==23501== 2. The instruction is legitimate but Valgrind doesn't handle it,
==23501== i.e. it's Valgrind's fault. If you think this is the case or
==23501== you are not sure, please let us know and we'll try to fix it.
==23501== Either way, Valgrind will now raise a SIGILL signal which will
==23501== probably kill your program.
==23501== Warning: client switching stacks? SP change: 0x5e5d2b0 -->
0x7feffeee0
==23501== to suppress, use: --max-stackframe=34244009008 or greater
This error is not reproduced in Debian Sid's valgrind 3.9.0-5.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic