Valgrind unsupported socket operation
-
Re: [Error: "valgrind" could not be started: ip address: Unsupported socket operation]
I have not seen any postings related to "valgrind" and "unsupported socket operation".
This error message occurs in the application output when i attempt to:
Analyze->Valgrind Memory Analyzer
OR
Analyzer->Valgrind Memory Analyzer with GDBThe ip address specified in the ERROR: message is the same as my computer as displayed in ifconfig
What does the "unsupported socket operation" message mean?
Could this be related to the way in which Valgrind was installed on my computer? -
@rnhwizard said in Valgrind unsupported socket operation:
Could this be related to the way in which Valgrind was installed on my computer?
In what way was it installed? Does it work if you run it outside of QtCreator?
-
@rnhwizard and to add to @jsulm,
- which operating system?
- which Creator and valgrind versions?
Regards
-
Installed from a tar
Ubuntu 18.04.2
QT Creator 4.9.2
Valgrind 3.15.0
download from valgrind-3.15.0.tar.bz2
install via:./configure --prefix=/usr/local/bin
make
make installRunning it from my terminal returns the following:
valgrind ls -l
failed to start tool "memcheck" for platform 'amd64-linux': no such file or directory
Note that my processor is an X86 not an "amd64-linux". -
@rnhwizard said in Valgrind unsupported socket operation:
memcheck" for platform 'amd64-linux':
Hi
This error is pretty common on google.
Try
https://www.linuxquestions.org/questions/linux-software-2/error-installing-valgrind-failed-to-start-tool-'memcheck'-850429/make distclean
-
I resolved the issue regarding memcheck by adding the appropriate lines to .bashrc.
I was able to run Memcheck in the QT IDE and it seems to be working appropriately.
It gives the following directions:
==14386== (action at startup) vgdb me ...
==14386==
==14386== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==14386== /path/to/gdb /home/otc_gui
==14386== and then give GDB the following command
==14386== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=14386
==14386== --pid is optional if only one valgrind process is running
==14386==When I run it with the GDB option it gives the PID 14386 but there is no apparent way to run the GDB with the provided Process identifier assigned.
I would like to run this from within the IDE as it is set up to a remote target via SSH. However, I am not sure how to invoke the GDB
properly with the provided PID. Is there somewhere to assign it? -
Hi @rnhwizard,
Have you tried Debug > Start Debugging > Attach to running Debug Server?
I resolved the issue regarding memcheck by adding the appropriate lines to .bashrc.
Can you please write what you did to help others with the same problem later?
Regards
-
To resolve the original issue:
As for current memcheck issue, in attempting to Attach the pid to the debugger I tried the following:
Step 1: Analyze->Valgrind Memory Analyzer with Debugger
Step 2: Debug->Attach to running application
The active Valgrind process was listed and matched the printed PID I displayed above.
However, when I attach the debugger to the active process QT immediately crashes with no warnings or errors.I looked into the Debug server option, but there is no way (that I can see) to link this to Valgrind.
