| Summary: | vex amd64->IR: unhandled instruction bytes: 0xF8 0x49 0xFF 0xE3 (clc) | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | neal <nnorwitz> |
| Component: | vex | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
neal
2006-04-15 23:02:25 UTC
This is a clc instruction which the amd64 decoder doesn't handle at the moment (the x86 decoder does). Fixed (vex r1613). Please verify. I still get this warning msg: --28776-- DWARF2 CFI reader: unhandled CFI instruction 0:10 --28776-- DWARF2 CFI reader: unhandled CFI instruction 0:10 However the test no longer crashes V any more. The ctypes test which used to crash V, doesn't pass. Though I'm not sure if that's because of a corner case wrt this instruction or something completely unrelated. Thanks for fixing. > The ctypes test which used to crash V, doesn't pass.
Hmm. Not good. Do you have any more details on that?
> ------- I still get this warning msg:
> --28776-- DWARF2 CFI reader: unhandled CFI instruction 0:10
This is with which version of the sources? I believe this is fixed
in the trunk.
This was checked out from a clean directory. neal@janus ~/build/valgrind $ ~/local/bin/valgrind --version valgrind-3.2.0.SVN neal@janus ~/build/valgrind $ svn info Path: . URL: svn://svn.valgrind.org/valgrind/trunk Repository UUID: a5019735-40e9-0310-863c-91ae7b9d1cf9 Revision: 5902 Node Kind: directory Schedule: normal Last Changed Author: sewardj Last Changed Rev: 5902 Last Changed Date: 2006-05-12 19:20:11 -0700 (Fri, 12 May 2006) Properties Last Updated: 2006-05-12 21:26:08 -0700 (Fri, 12 May 2006) neal@janus ~/build/python/svn/trunk $ svn info Path: . URL: svn+ssh://pythondev@svn.python.org/python/trunk Repository UUID: 6015fed2-1504-0410-9fe1-9d1591cc4771 Revision: 45987 Node Kind: directory Schedule: normal Last Changed Author: gerhard.haering Last Changed Rev: 45987 Last Changed Date: 2006-05-12 16:49:49 -0700 (Fri, 12 May 2006) Properties Last Updated: 2006-05-12 21:35:43 -0700 (Fri, 12 May 2006) I looked at this some more. > --28776-- DWARF2 CFI reader: unhandled CFI instruction 0:10 This is not a big deal; I'm inclined to ignore it for the time being. It will mean that stack unwinding will not work on some deeply obscure function, but too rare to put effort into fixing. > The ctypes test which used to crash V, doesn't pass. I was more concerned about this and went looking for a bug in Valgrind's amd64 CPU simulation. It turns out this test causes Python to generate bits of code on the fly and then run them, which fools Valgrind's default assumptions about self-modifying-code. You can get V to handle this correctly by specifying --smc-check=all (engage support for unfriendly self-modifying code). This reduces V's speed but makes it more robust: $ vTRUNK -q --tool=none ./python Lib/test/regrtest.py test_ctypes test test_ctypes failed -- Traceback (most recent call last): [...] vTRUNK -q --smc-check=all --tool=none ./python Lib/test/regrtest.py test_ctypes 1 test OK. |