|
From: Peng Du <imd...@gm...> - 2009-08-17 22:53:26
|
Hello, everyone I found the HotSpot JVM from both OpenJDK 1.6 and 1.7 running on Valgrind 3.4.1 on Linux (x86_64) crashes with the following error: ---------------- vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xAE 0x4 0x24 0x49 ==12704== valgrind: Unrecognised instruction at address 0x7aabc46. ==12704== Your program just tried to execute an instruction that Valgrind ==12704== did not recognise. There are two possible reasons for this. ==12704== 1. Your program has a bug and erroneously jumped to a non-code ==12704== location. If you are running Memcheck and you just saw a ==12704== warning about a bad jump, it's probably your program's fault. ==12704== 2. The instruction is legitimate but Valgrind doesn't handle it, ==12704== i.e. it's Valgrind's fault. If you think this is the case or ==12704== you are not sure, please let us know and we'll try to fix it. ==12704== Either way, Valgrind will now raise a SIGILL signal which will ==12704== probably kill your program. ---------------- The error occurred when I ran moderate (JFLAP.jar) to large Java app (SPECJbb2005), but not with "Hello World" kind small app. Running same tests on 32-bit Linux worked out of the box with no errors. The option --smc-check does not help either. The crash report generated by HotSpot indicates the problematic frame is: ~RuntimeStub::resolve_static_call. Might this be a bug in Valgrind's x86_64 ISA support? Thanks |
|
From: Vince W. <vi...@cs...> - 2009-08-18 00:51:35
|
> I found the HotSpot JVM from both OpenJDK 1.6 and 1.7 running on > Valgrind 3.4.1 on Linux (x86_64) crashes with the following error: > > ---------------- > vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xAE 0x4 0x24 0x49 I think this bug has already been reported: https://bugs.kde.org/show_bug.cgi?id=194402 Vince |