Fix valgrind incompatibility with glibc-2.43

[Douglas R. Reno]

While I was running the test suite for valgrind-3.26.0, I got some additional test failures from what I had last time I built it. One issue is with helgrind, and is related to the _dl_allocate_tls_init function not being suppressed correctly. The other issue is related to __is_decorate_maps_available, where another suppression is required.

For valgrind, the ltpchecks and test suite is really helpful for catching issues before they crop up in other packages that use valgrind for testing later :)

While we're at it, let's include the remainder of the fixes for valgrind-3.26.0 since there's only 7 of them, and also fix the ltpchecks test suite which fails to build currently against Linux 6.18.

[Douglas R. Reno]

Much, much better...

Before:

== 859 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls                    (stdoutB)
memcheck/tests/descr_belowsp             (stderr)
helgrind/tests/tc22_exit_w_lock          (stderr)
drd/tests/pth_detached3                  (stderr)
drd/tests/std_thread2                    (stderr)
drd/tests/tls_threads                    (stderr)

After:

== 865 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls                    (stdoutB)
drd/tests/pth_detached3                  (stderr)

No more issues with new glibc functions!

I'm unable to fix the ltpchecks test suite unfortunately. The new version that the LTP folks released (​https://github.com/linux-test-project/ltp/) has compilation issues with Linux 6.18.x, while the version included with valgrind-3.26.0 has problems with glibc-2.43. For now I'll just mention that it's broken.

​https://sourceware.org/git/?p=valgrind.git;a=log;h=refs/heads/VALGRIND_3_26_BRANCH is where I found these patches. All of them after " Set version to 3.26.1.GIT" have been applied.

[Randy McMurchy]

You are really good at this stuff, Doug. The project is fortunate that you volunteer and do such a great job. I know everyone appreciates your work, I just wanted to point it out redundantly.

[Douglas R. Reno]

Replying to randy:

You are really good at this stuff, Doug. The project is fortunate that you volunteer and do such a great job. I know everyone appreciates your work, I just wanted to point it out redundantly.

Thank you Randy, I really appreciate it! It's always very rewarding to work on this stuff, and it keeps my brain going.

[Douglas R. Reno]

Fixed at 76cb973236f8761a1f0b0afc8652eb97488a0825

[Randy McMurchy]

Replying to Douglas R. Reno:

It's always very rewarding to work on this stuff, and it keeps my brain going.

The other day I told my youngest son (Ivy League school grad) who aspires to be a writer, that I was going back to doing volunteer open source work again. He asked how much it paid. My reply to him was this:

"I don't need money. The time invested in writing things that help others learn and advance their skills makes it worthwhile. Many people contribute to open source projects, some have become successful doing it, while others like me just enjoy doing it."