Valgrind Memcheck fails to start in Qt Creator (Linux Mint 22.2 / Ubuntu 24.04)
-
Hi everyone,
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.0I tried to troubleshoot the issue using GoogleAI, but I couldn't solve it.
Here are the brief conclusions:-
Manual Run Works: Running the exact same binary via terminal with valgrind --tool=memcheck --smc-check=all ./my_app works perfectly.
-
The "memcmp" issue: Initially, Valgrind complained about missing memcmp redirections. This was solved by setting DEBUGINFOD_URLS="https://ubuntu.com".
-
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.
-
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!
-
-
Hi everyone,
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.0I tried to troubleshoot the issue using GoogleAI, but I couldn't solve it.
Here are the brief conclusions:-
Manual Run Works: Running the exact same binary via terminal with valgrind --tool=memcheck --smc-check=all ./my_app works perfectly.
-
The "memcmp" issue: Initially, Valgrind complained about missing memcmp redirections. This was solved by setting DEBUGINFOD_URLS="https://ubuntu.com".
-
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.
-
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!
@Tetsuzin72
I will just say that I use valgrind from Creator under Ubuntu 24.04 with no problem. But I may not be doing the same as you, and I use the much older Creator which comes with 24.04 so I don't know about newer ones.While you await a solution: if you really need to get this working, you could tell Creator to run a different "executable" for valgrind which is actually an executable shell script of yours. Then you can go through the command line arguments Creator passes to it and remove the ones you say it prepends but you do not want before passing on to the real
valgrindexecutable. Just saying. -
