Description of problem: Bug 720854 uncovered a problem where valgrind did not handle a PTEST instruction with the REX.W prefix. According to Jakub Jelinek and the Intel 64 and IA-32 Architectures Software Developer’s Manual (http://www.intel.com/Assets/PDF/manual/325383.pdf), that instruction does not support that prefix. I went through hotspot/src/cpu/x86/vm/assembler_x86.cpp and checked instructions against the Instruction Set Reference. The following instructions do not list REX.W as an option (with page numbers of the reference). MOVDQA (p. 3-671) MOVDQU (p. 3-674) PCMPESTRI (p. 4-85) PSRLQ (p. 4-244) PTEST (p. 4-262) The corresponding methods should probably call prefix_and_encode instead of prefixq_and_encode. Version-Release number of selected component (if applicable): java-1.6.0-openjdk-1.6.0.0-58.1.10.2.fc15.x86_64 tomcat6-6.0.30-6.fc15.noarch valgrind-3.6.1-4.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. Launch tomcat6 from valgrind (see options below) Actual results: valgrind raises a SIGILL signal Expected results: valgrind and tomcat would run Additional info: In /usr/sbin/tomcat6: JAVACMD="/usr/bin/valgrind --smc-check=all --trace-children=yes --log-file=/var/log/tomcat6/valgrind.out --leak-check=yes --tool=memcheck ${JAVACMD}"
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping