==969== Illegal opcode at address 0x380D858C ==969== at 0x80F0: ??? (in /mnt/nfs/a.out) valgrind: m_scheduler/scheduler.c:957 (run_thread_for_a_while): Assertion 'done_this_time >= 0' failed. ==969== at 0x38063FD0: report_and_quit (m_libcassert.c:260) ==969== by...
==26274== Illegal opcode at address 0x732CAB0 ==26274== at 0x732CAB0: ??? (in /opt/intel/composerxe-2011.3.174/ipp/lib/intel64/libippsy8.so.7.0) ==26274== by 0x5BD9EFE: (below main) (libc-start.c:226) I'm using that function in a much b...
==14222== ==14222== Process terminating with default action of signal 4 (SIGILL) ==14222== Illegal opcode at address 0x4073170 ==14222== at 0x4073170: __dl__Z26__libc_safe_arc4random_bufPvm (in /apex/com.android.runtime/bin/linker64) ==14222== by 0x4078377: __dl___libc_init...
argument 'lock_addr', which shows information about the lock at the given address only. - When using --history-level=full, the new Helgrind monitor command 'accesshistory <addr> [<len>]' will show the recorded accesses for <len> (or 1) bytes at <addr>. *...
Hi all, I am currently debugging an application with valgrind in a raspberry pi and I came across some "Illegal Instructions" issues on "libcoreclr.so". Not sure if these instructions are actually being executed, however, as they are bei...
Component:valgrind Version:rawhide Hardware:All OS:Linux Priority:low Severity:medium Target Milestone:--- Assignee:Jakub Jelinek QA Contact:Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Depends On: Blocks: TreeView+depends on/blocked...
==26274== Illegal opcode at address 0x732CAB0 ==26274== at 0x732CAB0: ??? (in /opt/intel/composerxe-2011.3.174/ipp/lib/intel64/libippsy8.so.7.0) ==26274== by 0x5BD9EFE: (below main) (libc-start.c:226) I'm using that function...
argument 'lock_addr', which shows information about the lock at the given address only. - When using --history-level=full, the new Helgrind monitor command 'accesshistory <addr> [<len>]' will show the recorded accesses for <len> (or 1) bytes at <addr>. *...
==26274== Illegal opcode at address 0x732CAB0 ==26274== at 0x732CAB0: ??? (in /opt/intel/composerxe-2011.3.174/ipp/lib/intel64/libippsy8.so.7.0) ==26274== by 0x5BD9EFE: (below main) (libc-start.c:226) I'm using that function in a much bigger code ...
argument 'lock_addr', which shows information about the lock at the given address only. - When using --history-level=full, the new Helgrind monitor command 'accesshistory <addr> [<len>]' will show the recorded accesses for <len> (or 1) bytes at <addr>. *...