Re: Valgrind-3.23.0.RC2 is available for testing

On 25-04-24 08:50, Simon Sobisch wrote:
> I've compiled and tried to run the RC2 on some environments, using
> 
> 1. Find just a minor patch for configure.ac to improve help output and 
> keep the style of the file (two missing spaces visible in "configure 
> --help"; tabs/line breaks).
> 
> 2. One thing that _may_ be an old issue: all the make targets check, 
> regtest and perf fail because of missing g++ on building "bug464969", 
> while configure and make pass.

> 
> 3. "make regtest" fails in my out-of-tree build (where "make check" 
> executed without errors)
> 
> ../gdbserver_tests/make_local_links /usr/bin/gdb
> if /usr/bin/perl tests/vg_regtest gdbserver_tests memcheck cachegrind 
> callgrind helgrind drd massif dhat lackey none exp-bbv ; then \
>     tests/post_regtest_checks /home/build/valgrind-3.23.0.RC2/build/.. 
> gdbserver_tests memcheck cachegrind callgrind helgrind drd massif dhat 
> lackey none exp-bbv; \
> else \
>     tests/post_regtest_checks /home/build/valgrind-3.23.0.RC2/build/.. 
> gdbserver_tests memcheck cachegrind callgrind helgrind drd massif dhat 
> lackey none exp-bbv; \
>     false; \
> fi
> sh: 0: cannot open 
> /home/build/valgrind-3.23.0.RC2/build/tests/platform_test: No such file
> sh: 0: cannot open 
> /home/build/valgrind-3.23.0.RC2/build/tests/platform_test: No such file
> sh: 0: cannot open 
> /home/build/valgrind-3.23.0.RC2/build/tests/platform_test: No such file
> sh: 0: cannot open 
> /home/build/valgrind-3.23.0.RC2/build/tests/platform_test: No such file
> -- Running  tests in memcheck/tests/linux ------------------------------
> vg_regtest: `./filter_stderr' not found or not a file (.)
> /bin/bash: line 4: tests/post_regtest_checks: No such file or directory
> make: *** [Makefile:1442: regtest] Error 1
> 
> 
> 4. "make perf" outputs
> == 0 programs, 0 timings =================

Hi

I'll apply the configure patch after the release.

Not having a C++ compiler. I can just about imagine someone building and 
using Valgrind without a C++ compiler - in some situations it might make 
automatic package building faster. Is there any benefit to being able to 
run only the non-C++ testcases?

It's a while since I tried an out of tree build. There is a bugzilla 
item for that https://bugs.kde.org/show_bug.cgi?id=333628

What platform did you use for "make perf"?

A+
Paul


_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users