https://bugs.kde.org/show_bug.cgi?id=505673
--- Comment #2 from Ismail <[email protected]> --- (In reply to Paul Floyd from comment #1) > Does this happen with Valgrind 3.25.1? > > Can you provide a reproducer? yes , ➔ > minishell --45966-- VALGRIND INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS) - exiting --45966-- si_code=2; Faulting address: 0x4006331; sp: 0x1002eea5a0 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==45966== at 0x581DF671: disInstr_AMD64_WRK (guest_amd64_toIR.c:32279) ==45966== by 0x581E0469: disInstr_AMD64 (guest_amd64_toIR.c:32687) ==45966== by 0x5816D2F6: disassemble_basic_block_till_stop.constprop.0 (guest_generic_bb_to_IR.c:956) ==45966== by 0x5816DAE4: bb_to_IR (guest_generic_bb_to_IR.c:1365) ==45966== by 0x58151515: LibVEX_FrontEnd (main_main.c:611) ==45966== by 0x58151EF6: LibVEX_Translate (main_main.c:1287) ==45966== by 0x5805BC15: vgPlain_translate (m_translate.c:1835) ==45966== by 0x5809C836: handle_tt_miss (scheduler.c:1144) ==45966== by 0x5809C836: vgPlain_scheduler (scheduler.c:1557) ==45966== by 0x58106A4D: thread_wrapper (syswrap-linux.c:102) ==45966== by 0x58106A4D: run_a_thread_NORETURN (syswrap-linux.c:155) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 45966) ==45966== at 0x4006331: out_fd (redirections.c:21) ==45966== by 0x400AC1A: redirection (execute_redirections.c:25) ==45966== by 0x400AD03: execute_redirections (execute_redirections.c:52) ==45966== by 0x4009577: execute_ast (execute_ast.c:65) ==45966== by 0x4007124: execution (execution.c:54) ==45966== by 0x400B880: read_eval_print_loop (main.c:149) ==45966== by 0x400B9AC: main (main.c:185) client stack range: [0x1FFEFE6000 0x1FFF000FFF] client SP: 0x1FFEFFFB80 valgrind stack range: [0x1002DEB000 0x1002EEAFFF] top usage: 18104 of 1048576 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. ➜ MINI-SHELL git:(main) ✗ valgrind --version valgrind-3.25.1 -- You are receiving this mail because: You are watching all bug changes.
