|
From: Rak <ra...@ho...> - 2005-10-14 14:49:47
|
Hi, Valgrind does not crash but it gives me this error messgae and abort the program. Is this a bug or I am doing something wrong? Thanks, Rak xeon%uname -a Linux xeon 2.4.21-15.EL #1 SMP Thu Apr 22 00:09:47 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux xeon%valgrind --tool=memcheck --num-callers=30 ./pro ==14886== Memcheck, a memory error detector. ==14886== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. ==14886== Using LibVEX rev 1419, a library for dynamic binary translation. ==14886== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. ==14886== Using valgrind-3.1.SVN, a dynamic binary instrumentation framework. ==14886== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. ==14886== For more details, rerun with: -v ==14886== ==14886== Warning: set address range perms: large range 257616336, a 0, v 1 ==14886== Warning: set address range perms: large range 188918656, a 0, v 1 ==14886== Warning: set address range perms: large range 626458864, a 0, v 1 . . . ==14886== Warning: set address range perms: large range 257616336, a 0, v 1 **NOTE - REALLOCATING MEMORY vex amd64->IR: unhandled instruction bytes: 0xF 0xAD 0xC2 0xD3 ==14886== Your program just tried to execute an instruction that Valgrind ==14886== did not recognise. This might be because your program has a bug ==14886== and erroneously jumped to a non-code location. If you are running ==14886== Memcheck, you might have just seen a warning about a bad jump, ==14886== which is a good indication that this is so. Or it might be ==14886== because the instruction is unimplemented in Valgrind; if you ==14886== think this is the case, or you are not sure, please let us know. ==14886== ==14886== Process terminating with default action of signal 4 (SIGILL) ==14886== Illegal opcode at address 0x2525F67 ==14886== at 0x2525F67: _normal64 (in /u/xeon/working/pro) ==14886== ==14886== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 5) ==14886== malloc/free: in use at exit: 2,302,994,016 bytes in 878,618 blocks. ==14886== malloc/free: 879,341 allocs, 723 frees, 2,303,707,200 bytes allocated. |
|
From: Tom H. <to...@co...> - 2005-10-14 15:00:40
|
In message <loo...@po...>
ra...@ho... wrote:
> Valgrind does not crash but it gives me this error messgae and abort the
> program. Is this a bug or I am doing something wrong?
It's a bug - specifically an instruction that is not supported. Please
raise a bug for this on the bug tracker.
> vex amd64->IR: unhandled instruction bytes: 0xF 0xAD 0xC2 0xD3
That's "SHRD %cl,Gv,Ev" which the amd64 engine doesn't support currently.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Rak <ra...@ho...> - 2005-10-14 17:51:40
|
Tom Hughes <tom <at> compton.nu> writes: > > In message <loom.20051014T163455-681 <at> post.gmane.org> > rak_25 <at> hotmail.com wrote: > > > Valgrind does not crash but it gives me this error messgae and abort the > > program. Is this a bug or I am doing something wrong? > > It's a bug - specifically an instruction that is not supported. Please > raise a bug for this on the bug tracker. > > > vex amd64->IR: unhandled instruction bytes: 0xF 0xAD 0xC2 0xD3 > > That's "SHRD %cl,Gv,Ev" which the amd64 engine doesn't support currently. > > Tom > Submited Bug 114412: vex amd64->IR: unhandled instruction bytes: 0xF 0xAD 0xC2 0xD3 Thanks, Rak |
|
From: John R.
|
> vex amd64->IR: unhandled instruction bytes: 0xF 0xAD 0xC2 0xD3 shrd %cl,%eax,%edx # 64-bit shift: graphics or crypto, etc. roll %cl, ... -- |