I am experiencing an issue where Valgrind (Memcheck) fails to run my project from within Qt Creator 19 on Linux Mint 22.2 (based on Ubuntu 24.04).

When I start the Analysis (Analyze > Valgrind Memory Analyzer), the process exits almost immediately (within 1 second) with no error message in the "Valgrind" output pane, only "Process exited with return value" and "Analyzing finished."

The Environment:
OS: Linux Mint 22.2 (Ubuntu 24.04 base)
Qt Creator: 19.x
Valgrind: 3.22.0

I tried to troubleshoot the issue using GoogleAI, but I couldn't solve it.
Here are the brief conclusions:

1. Manual Run Works: Running the exact same binary via terminal with valgrind --tool=memcheck --smc-check=all ./my_app works perfectly.

2. The "memcmp" issue: Initially, Valgrind complained about missing memcmp redirections. This was solved by setting DEBUGINFOD_URLS="https://ubuntu.com".

3. The Integration Conflict: Even with DEBUGINFOD_URLS set in the Run Environment, Qt Creator still fails. The logs show that Qt Creator forces several flags: --xml=yes --xml-socket=... --vgdb-error=0.

4. The Conclusion: It seems there is a compatibility issue between how Qt Creator 19 handles XML/VGDB sockets and the way Valgrind/glibc behaves in the latest Ubuntu 24.04-based distributions. Adding --vgdb=no or --xml=no to "Extra Memcheck arguments" does not help because Qt Creator prepends its own conflicting flags.

Has anyone found a workaround to make the integrated Valgrind UI work on Noble-based systems, or is this a known regression in the IDE's interaction with the newer Valgrind/glibc stack?

Thanks in advance!