https://bugs.kde.org/show_bug.cgi?id=510200
--- Comment #2 from [email protected] --- Right ... I've tweaked the LTP testsuite so that the testcase doesn't fork (ugh :), and then: $ gdb -q -ex 'set auto-load safe-path /' -ex 'set remote exec-file ./mknod06' -ex 'set sysroot /' -ex 'target extended-remote | vgdb --multi --vargs -q --tool=memcheck' ./mknod06 Reading symbols from ./mknod06... Remote debugging using | vgdb --multi --vargs -q --tool=memcheck (gdb) b run Breakpoint 1 at 0x401ec0: file mknod06.c, line 42. (gdb) r Starting program: /home/mcermak/WORK/LTP/testcases/kernel/syscalls/mknod/mknod06 relaying data between gdb and process 4179032 Loaded /usr/local/libexec/valgrind/valgrind-monitor.py Type "help valgrind" for more info. tst_buffers.c:57: TINFO: Test is using guarded buffers tst_tmpdir.c:316: TINFO: Using /tmp/LTP_mknIKjroF as tmpdir (tmpfs filesystem) tst_test.c:2024: TINFO: LTP version: 20250930 tst_test.c:2027: TINFO: Tested kernel: 6.12.11-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jan 24 04:59:58 UTC 2025 x86_64 tst_kconfig.c:88: TINFO: Parsing kernel config '/lib/modules/6.12.11-200.fc41.x86_64/config' tst_test.c:1843: TINFO: Overall timeout per run is 8h 19m 30s Breakpoint 1, run (i=0) at mknod06.c:42 42 TST_EXP_FAIL(mknod(tc->pathname, MODE_FIFO_RWX, 0), tc->exp_errno, "%s", (gdb) p tc->pathname $1 = 0x485dffe 'a' <repeats 200 times>... (gdb) s __GI___errno_location () at errno-loc.c:25 25 { (gdb) n 26 return &errno; (gdb) n --4179032-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --4179032-- si_code=2; Faulting address: 0x485F000; sp: 0x1002ef6d00 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==4179032== at 0x5801028D: mc_is_defined_asciiz (mc_main.c:4412) ==4179032== by 0x5801028D: check_mem_is_defined_asciiz (mc_main.c:4490) ==4179032== by 0x58099D91: vgPlain_client_syscall (syswrap-main.c:2410) ==4179032== by 0x58095CFA: handle_syscall (scheduler.c:1214) ==4179032== by 0x58097BE6: vgPlain_scheduler (scheduler.c:1588) ==4179032== by 0x581014BA: thread_wrapper (syswrap-linux.c:102) ==4179032== by 0x581014BA: run_a_thread_NORETURN (syswrap-linux.c:154) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 259 (lwpid 4179032) ==4179032== at 0x495C017: mknodat (mknodat.c:33) ==4179032== by 0x401F05: run (mknod06.c:42) ==4179032== by 0x40AEDA: run_tests (tst_test.c:1686) ==4179032== by 0x40AEDA: testrun (tst_test.c:1752) ==4179032== by 0x40AEDA: fork_testrun.isra.0 (tst_test.c:1881) ==4179032== by 0x40DD3D: tst_run_tcases (tst_test.c:2044) ==4179032== by 0x401DCD: main (tst_test.h:738) client stack range: [0x1FFEFFC000 0x1FFF000FFF] client SP: 0x1FFEFFF4B8 valgrind stack range: [0x1002DF7000 0x1002EF6FFF] top usage: 17848 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. Program terminated with signal 0, Signal 0. The program no longer exists. (gdb) -- You are receiving this mail because: You are watching all bug changes.
