|
From: Christoph B. <bar...@or...> - 2005-12-05 22:16:49
|
Hi, I've just got the following error with valgrind 3.1.0: ==01:02:38:32.373 2400== Warning: set address range perms: large range 268439552, a 1, v 1 ==01:02:50:00.615 2400== Warning: set address range perms: large range 268439552, a 0, v 0 --01:02:52:57.936 2400-- INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS) - exiting --01:02:52:57.936 2400-- si_code=2; Faulting address: 0x4F4029EC; sp: 0x495A44610 valgrind: the 'impossible' happened: Killed by fatal signal ==01:02:52:57.936 2400== at 0x700C0FCD: disInstr_AMD64 (toIR.c:7954) ==01:02:52:57.936 2400== by 0x7008F238: bb_to_IR (bb_to_IR.c:187) ==01:02:52:57.936 2400== by 0x700688E5: LibVEX_Translate (vex_main.c:416) ==01:02:52:57.936 2400== by 0x7002354D: vgPlain_translate (libvex_basictypes.h:154) ==01:02:52:57.936 2400== by 0x70034759: handle_tt_miss (scheduler.c:596) ==01:02:52:57.936 2400== by 0x70034B81: vgPlain_scheduler (scheduler.c:717) ==01:02:52:57.936 2400== by 0x7004785E: thread_wrapper (syswrap-linux.c:86) ==01:02:52:57.936 2400== by 0x70047955: run_a_thread_NORETURN (syswrap-linux.c:119) ==01:02:52:57.936 2400== by 0x70047A86: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:206) ==01:02:52:57.936 2400== by 0x70050F2E: (within /usr/local/opt/x86_64-20050615/lib/valgrind/amd64-linux/memcheck) sched status: running_tid=3 What could be wrong, and how to avoid it? Christoph Bartochek |