|
From: Paul F. <pa...@fr...> - 2007-06-11 15:04:18
|
Hi again One of my colleagues recently had a Valgrind crash with the following stack: --12039-- VALGRIND INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS) - exiting --12039-- si_code=2; Faulting address: 0x9338308; sp: 0x646EB53C valgrind: the 'impossible' happened: Killed by fatal signal ==12039== at 0x380C844B: disInstr_X86_WRK (toIR.c:7190) ==12039== by 0x380DA965: disInstr_X86 (toIR.c:13047) ==12039== by 0x380A8CEA: bb_to_IR (bb_to_IR.c:228) ==12039== by 0x38075E6C: LibVEX_Translate (vex_main.c:426) ==12039== by 0x3802B3BC: vgPlain_translate (m_translate.c:1097) ==12039== by 0x3803850A: handle_tt_miss (scheduler.c:693) ==12039== by 0x38038ADB: vgPlain_scheduler (scheduler.c:865) ==12039== by 0x3804CA86: thread_wrapper (syswrap-linux.c:87) ==12039== by 0x3804CB9D: run_a_thread_NORETURN (syswrap-linux.c:120) (with Valgrind 3.2.1 on RHEL 3.0 kernel 2.4.21-4.ELsmp) Looking at toIR.c:7190, it seems to be just accessing a table - not an obvious site for a sigbus. I don't have much of a clue how to proceed. A+ Paul |