514659 ltp 20250930 vs linux 6.18.3 doesn't build
514762 Many "Bad file descriptor" messages when using --track-fds=yes and
-d on systems without /proc
-515265 Add SSE4.1 BLENDPS and PBLENDW instruction for x86 32 bit
+515183 Error occurred while executing the command
+ `valgrind --num-callers=1 ./hello_world`
+515265 Add SSE4.1 BLENDPS and PBLENDW instruction for x86 32 bit
+
To see details of a given bug, visit
https://bugs.kde.org/show_bug.cgi?id=XXXXXX
else if VG_INT_CLO (arg, "--dump-error", VG_(clo_dump_error)) {}
else if VG_INT_CLO (arg, "--input-fd", VG_(clo_input_fd)) {}
else if VG_INT_CLO (arg, "--sanity-level", VG_(clo_sanity_level)) {}
- else if VG_BINT_CLO(arg, "--num-callers", VG_(clo_backtrace_size), 1,
+ else if VG_BINT_CLO(arg, "--num-callers", VG_(clo_backtrace_size), 2,
VG_DEEPEST_BACKTRACE) {}
else if VG_BINT_CLO(arg, "--num-transtab-sectors",
VG_(clo_num_transtab_sectors),
will make Valgrind run a bit more slowly and take a bit more
memory, but can be useful when working with programs with
deeply-nested call chains.</para>
+
+ <para>The minimum value for this is 2. A value of 1 is not allowed
+ for two reasons. Firstly, some of the default suppressions use
+ "<computeroutput>...</computeroutput>" which is forbidden with
+ <computeroutput>--num-callers=1</computeroutput>. Secondly, it would
+ make leak suppressions match all allocations using the allocation
+ function (e.g., <computeroutput>malloc</computeroutput>).</para>
+
</listitem>
</varlistentry>
new_delete_mismatch_size_supp.stderr.exp-32 \
new_delete_mismatch_size_supp.vgtest \
new_delete_mismatch_size_supp.supp \
+ num_callers_1.stderr.exp num_callers_1.vgtest \
deep-backtrace.vgtest deep-backtrace.stderr.exp \
demangle.stderr.exp demangle.vgtest \
big_debuginfo_symbol.vgtest \
--- /dev/null
+valgrind: Bad option: --num-callers=1
+valgrind: '--num-callers' argument must be between 2 and 500
+valgrind: Use --help for more information or consult the user manual.
--- /dev/null
+prog: ../../tests/true
+vgopts: -q --num-callers=1