https://bugs.kde.org/show_bug.cgi?id=504341
Bug ID: 504341
Summary: Valgrind killed by LTP syscall testcase setrlimit05
Classification: Developer tools
Product: valgrind
Version First 3.25 GIT
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: mcer...@redhat.com
Target Milestone: ---
The setrlimit05 LTP testcase kills valgrind. Attached patch fixes the problem
for me:
41$ valgrind --version
valgrind-3.26.0.GIT
41$ /usr/local/bin/valgrind --tool=none
/home/mcermak/WORK/ltp/ltp/testcases/kernel/syscalls/setrlimit/setrlimit05
==3409713== Nulgrind, the minimal Valgrind tool
==3409713== Copyright (C) 2002-2024, and GNU GPL'd, by Nicholas Nethercote et
al.
==3409713== Using Valgrind-3.26.0.GIT and LibVEX; rerun with -h for copyright
info
==3409713== Command:
/home/mcermak/WORK/ltp/ltp/testcases/kernel/syscalls/setrlimit/setrlimit05
==3409713==
tst_test.c:1945: TINFO: LTP version: 20250130-253-g4a0e3a8fa
tst_test.c:1949: TINFO: Tested kernel: 6.12.9-200.fc41.x86_64 #1 SMP
PREEMPT_DYNAMIC Thu Jan 9 16:05:40 UTC 2025 x86_64
tst_kconfig.c:88: TINFO: Parsing kernel config
'/lib/modules/6.12.9-200.fc41.x86_64/config'
tst_test.c:1765: TINFO: Overall timeout per run is 0h 00m 30s
--3409716-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--3409716-- si_code=2; Faulting address: 0x483F000; sp: 0x100288dd20
valgrind: the 'impossible' happened:
Killed by fatal signal
host stacktrace:
==3409716== at 0x58086D85: vgSysWrap_linux_sys_prlimit64_before
(syswrap-linux.c:2303)
==3409716== by 0x58015401: vgPlain_client_syscall (syswrap-main.c:2410)
==3409716== by 0x5801197A: handle_syscall (scheduler.c:1214)
==3409716== by 0x58013856: vgPlain_scheduler (scheduler.c:1588)
==3409716== by 0x5807EE7A: run_a_thread_NORETURN (syswrap-linux.c:102)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 302 (lwpid 3409716)
==3409716== at 0x493D125: setrlimit (setrlimit64.c:40)
==3409716== by 0x401F36: verify_setrlimit (setrlimit05.c:29)
==3409716== by 0x40B91B: fork_testrun.isra.0 (tst_test.c:1592)
==3409716== by 0x40DC63: tst_run_tcases (tst_test.c:1963)
==3409716== by 0x401E0D: main (tst_test.h:729)
client stack range: [0x1FFEFFC000 0x1FFF000FFF] client SP: 0x1FFEFFF7B8
valgrind stack range: [0x100278E000 0x100288DFFF] top usage: 10600 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.
setrlimit05.c:60: TFAIL: child exited with 1
==3409715==
Summary:
passed 0
failed 1
broken 0
skipped 0
warnings 0
==3409713==
41$
--
You are receiving this mail because:
You are watching all bug changes.
