I'am trying to debug the qt application which i made and placed on VmWare. I followed this guide https://www.vmware.com/support/ws5/doc/ws_devices_serial_host_app_to_vm.html
https://www.vmware.com/support/ws5/doc/ws_devices_serial_advanced_example_debugging.html
I have the 'cdb' debugger installed so my vmware shared pipe is \\.\pipe\com_1 i'm running the cdb with arguments: cdb -server npipe:pipe=\\.\pipe\com_1 -v C:\tests\clean_deploy\app.exe on the Virtual Machine. I'am assuming that cdb will use the \\.\pipe\com_1 to listen for the connections. On my OS(Windows 7) i run the qt->debugging->attach to remote cdb session and set the connection string like this npipe:server=server,pipe=\\.\pipe\com_1
And i get in qt log:
Debugging Started
Debugging Finished
Without anything.
How do you debug an application on the vmware with cdb server using external pipe, from the qt cdb enviroment ??
Related
I am developing a qml application using QtCreator which must be run and debugged over a remote linux machine. The application must be run over eglfs platfrom and hence remote machine does not have X or wayland running.
The GUI must be displayed over the remote machine display and not to be forwarded over ssh tunnel to the local machine.
How can I make it done?
QtCreator 9.0.0
Qt 5.15.2
Both remote and local machines run Linux.
If I don't set any specific settings in QtCreator, by running the application, I get
Starting /home/pi/app/app --platform eglfs on RaspberryPi...
Cannot create window: no screens available
and if set enable checkbox Forward to local display in Project > Run settings, I'll get the app running on the local display over eglfs platform which I don't want to.
I've been setting up remote debugging for an embedded Linux target. I've tested that I have the correct combination of gdbserver running on the target and gdb client running on my workstation. I can start the server and on the workstation side run:
(gdb) target remote 10.28.22.226:2345
and I can list source and step just fine.
In Qt Creator I have configured a device. In that window I specify the GDB server executable: gdbserver (see pic).
I also configure the cross debugger in the 'Build & Run' Debuggers tab as shown below:
In this case, I have manually started the gdbserver with my executable on the target with port 2345. To start debugging with Qt Creator, I choose the Debug->Start Debugging->Attach to running Debug server pulldown menu. It gives me the prompt shown below, where I enter the server port (2345). I give it the appropriate kit and local executable (copy of the executable on the remote target).
After I hit OK, it seems to run the gdb client locally with a few commands, then times out trying to communicate with the gdbserver. I have debug logging turned on with the server, so I know the server never sees anything from the client run from Qt Creator. Additionally, I did Window->Views->Debugger Log to help me get a better idea of what was going on. The log shows the correct IP address and port for my device, but I don't see anything that looks like a 'target remote IP:port' call.
I'm looking for a hint or reference here. I seem to be a bit stuck at the moment. Thanks!
EDIT: additional information - I've verified that my gdb client has support for python compiled in. I see that Qt Creator requires python support. I also have further support that nothing ever goes out on the wire from Qt Creator. I did a wireshark capture and don't see anything going to port 2345 on the target.
Alternately, if anyone would share their Qt Creator debugger-log output with me so I can compare, that would be helpful.
Avoid Qt Creator 4.5-beta1. It seems 4.5RC1 doesn't have this problem. I was able to do remote debugging using the method described above just fine.
Even QtCreator 4.5.0 seems to have the same bug.
The only workaround I've found is to start the GDB server manually on the remote target: with "top" I get the pid of the remote process to debug then I run the following command: gdbserver --attach remote ip:remote port pid.
After the server is listening, I finally choose: "Attach to Running Debug" server".
Maybe you can write a server start script on target which include the above statement...
In Java
java -agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=n <other arguments>
allows us to
Start an application and suspends it
opens up a socket (dt_socket) using Java Debug Wire Protocol - Allows to debug remotely
Hosted on 8000 port
We can run this on a remote Linux Server and yet debug it on our own Desktop (even Windows) environment using either Netbeans or IntelliJ or other feature rich IDEs.
Is something of the sorts possible in C++ with visual studio community/code ? If so how.
PS: I know of ddd (data display debugger) & gdb
Yes, you can (using gdb).
Follow the manual.
There may be some IDE using gdb as backend.
I followed the steps in this link
and I manage to debug a binary which resides in linux host from my windows machine from command prompt.
I have gdbserver in linux and I installed gdb with the help of mingw in windows. As I told I can prompt "target remote x.x.x.x:10000 test" to command in windows and debug my test application.
My problem is I can't do the same with eclipse gui, it seems to me it has tones of buttons, options but they make no sense to me.
I am choosing debug_configurations-->C/C++ Remote Application(the only one which allows me to input linux machine ip/port), in "Main" tab to connection I am inputting my linux ip. In same menu under Debugger tab I am inputting my window's gdb path and gdbserver port.
After doing all those I believe I gave enough info to eclipse for connect gdb server but it never enough for eclipse. I am checking gdbserver logs by starting gdbserver with --debug, gdbserver never gets triggered, it does not writes a single line of log. Eclipse even does not starts a connection. But instead it gives me a error like "Error during file upload." which makes no sense to me.
I am using "Eclipse Version: Juno Service Release 2" . Any help will be appreciated .
I believe that the "C/C++ Remote Application" option uses Eclipse's RDT (Remote Development Tools) and RSE (Remote System Explorer) to connect, upload, execute, and debug the application itself. It
If all you want to do is connect to a gdbserver, then create a "C/C++ Attach to Application" debug configuration, and under the Debugger tab, set Debugger to gdbserver.
I also encountered this error message for other reason on Eclipse version 2019-09 R (4.13.0).
I very recommend to read paragraph "How do I debug a remote application?" from this great guide.
It explains which of three remote debugging options you should be using - Automatic Remote Launcher, Manual Remote Launcher and Remote Attach Launcher and how to use each one.
I was using the wrong launcher and hence got the error, while on the remote side gdbserver was listening and waiting for a connection. Switching to Manual Remote Launcher solved it.
for example it says:
If you don't have RSE installed, you cannot use the "Automatic Remote
Launch"
RSE = Remote System Explorer End-User Runtime
Launcher setting is configured from the bottom of the Remote Debug Configuration window - "Using GDB (DSF) Automatic/Manual Remote Debugging Launcher".
I'm trying to debug a C++ application which is running on a Linux box. This application will not build on OS X. I've got the app running on the Linux box, and I can start gdbserver for remote debugging. But since the application doesn't build on OS X, is there a way to use Eclipse on OS X to still debug the app?
Another way, assuming the remote Linux box is an SSH server and has gdb, is to run gdb on it thru ssh, e.g.
ssh remotelinuxbox gdb -tui prog