https://bugs.kde.org/show_bug.cgi?id=502842
Bug ID: 502842
Summary: Unhandled instruction bytes 0x62 0xF2 0x7D 0x8 0x7C
0xC6 0xC4 0xE2 (HDF5)
Classification: Developer tools
Product: valgrind
Version: 3.22.0
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: leomolinar...@gmail.com
Target Milestone: ---
Hi,
I'm running an application in MFEM, relying on NETCDF and HDF5 libraries.
Whenever running memcheck it throws a SIGILL due to unrecongnized instructions.
I'm wondering if it's a valgrind issue or I should look into how these
libraries are being installed (at the moment HDF5 is being downloaded by
PETSC).
vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0x7D 0x8 0x7C 0xC6 0xC4
0xE2 0x7vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0x7D 0x8 0x7C
0xC6 0xC4 0xE2 0x79 0x47
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==35693== valgrind: Unrecognised instruction at address 0xdb62ca1.
==35693== at 0xDB62CA1: H5FD__sec2_open (H5FDsec2.c:313)
==35693== by 0xDB41CD0: H5FD_open (H5FD.c:768)
==35693== by 0xDB2CE5D: H5F_open (H5Fint.c:1850)
==35693== by 0xDD60312: H5VL__native_file_open (H5VLnative_file.c:127)
==35693== by 0xDD4D8F4: H5VL__file_open (H5VLcallback.c:3674)
==35693== by 0xDD4D8F4: H5VL_file_open (???:3823)
==35693== by 0xDB2185C: H5F__open_api_common (H5F.c:794)
==35693== by 0xDB214FC: H5Fopen (H5F.c:835)
==35693== by 0xD836523: nc4_H5Fopen (in /usr/local/lib/libnetcdf.so.19.2.2)
==35693== by 0xD8352E5: nc4_open_file (in
/usr/local/lib/libnetcdf.so.19.2.2)
==35693== by 0xD8349F9: NC4_open (in /usr/local/lib/libnetcdf.so.19.2.2)
==35693== by 0xD7B898F: NC_open (in /usr/local/lib/libnetcdf.so.19.2.2)
==35693== by 0xD7B8564: nc_open (in /usr/local/lib/libnetcdf.so.19.2.2)
==35693== Your program just tried to execute an instruction that Valgrind
==35693== did not recognise. There are two possible reasons for this.
==35693== 1. Your program has a bug and erroneously jumped to a non-code
==35693== location. If you are running Memcheck and you just saw a
==35693== warning about a bad jump, it's probably your program's fault.
==35693== 2. The instruction is legitimate but Valgrind doesn't handle it,
==35693== i.e. it's Valgrind's fault. If you think this is the case or
==35693== you are not sure, please let us know and we'll try to fix it.
==35693== Either way, Valgrind will now raise a SIGILL signal which will
==35693== probably kill your program.
SOFTWARE/OS VERSIONS
Linux ada 5.15.0-130-generic #140-Ubuntu SMP, x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are watching all bug changes.
