Error when Visual Studio Remote Debugging with GDB - c++

I have a sample c++ application which builds and runs fine in a Red Hat installation.
I wanted to have the source code of this application in my windows machine so I can create a Visual Studio project and use Visual Studio 2017's new features which makes it possible to build and debug programs on a Linux server.
I successfully managed the following
Create a 'make file' project using Visual Studio CE 2017
Connect to the remote server and build by invoking make command at
the server
My remote debugger settings are as follows
Remote Build Settings are as follows
General Settings are as follows
However, when I try to debug the program via Visual Studio (using gdb in the server) following error occurs
Since this doesn't reveal much, I enabled verbose mode (in GDB) and following is the verbose output. Apparently, GDB crashes after loading symbols for one of the source files.
Furthermore, I can manually GDB the binary in the Linux Server without any problems

Related

SDL driver fails when starting debug session on remote linux

On Win10, I have a visual studio c++ project for linux that uses the SDL2 driver. The target machine is a VirtualBox - Ubuntu 18.04.
I configured Visual studio to compile remotely on the target system, which works fine.
Running the output file from console on the remote machine shows that SDL uses the XServer:
SDL_GetCurrentVideoDriver: x11
When I start debugging from visual studio (starts GNU debugger gdb on remote side):
SDL_Init error: No available video device
SDL_GetCurrentVideoDriver: null
starting gdb from remote anyway works as expected:
gdb ./myProgram
(gdb) run
But this doesn't let me debug in visual studio, which i'm looking forward to. Any idea ?
In Project Settings:
Configuration Properties -> Debugging -> Pre-Launch Command -> export DISPLAY=:0

Remote Debugging with Microsoft Embedded Visual C++

I need to attach remote debugger to the process running on Telmet320 device. The executable for that device is build using Microsoft Embedded Visual C++ 4.0. I have a connected device, source of application and Embedded Visual Studio installed on my desktop. But I do not see a possiblity for the remote debuggin in Visual Studio itself. Also I did not find remote tool for Embeded Visual studio (Not sure if they are exist at all).
Any help will be very valuable.
Found a solution. In Embedded Visula C++ goto to Build -> Start Debug -> Attach to WCE Process ...

Remote debugging(c++) with visual studio code

I searched for how to open and edit file located on remote server via local visual studio code(IDE). But I also wanted to do remote debugging, which means I will control the gdb command(via GUI)from the IDE instead of terminal.
I checked this link, but it is for node.js.
Can someone help me with this.
I use GDB extension for Visual Studio to debug my applications on remote linux machine.
Check out : extension
For reference See: link
In case you are developing apps on linux you may want to see the Linux workload from visual studio installer.

Error when remote debugging a C++ app running on Linux machine with gdbserver

I'm trying to get the remote debugging to work on Visual Studio 2017 in Windows. I'm using the gdbserver option in Visual Studio project properties. The project is a make file project created in Visual Studio 2017. I'm getting following error in the output window.
And getting following error in Linux Console output window
What could be the reason for these errors?

Debugging x64 application (C++) using visual studio 2012

I have a visual studio 2012 C++ application which compiles and run, but doesn't stop on breakpoints.
I already installed remote debugger (x64) and also run it and configure it for remote debugging.
In visual studio I tried boith remote debug and local debug, but both of them generate same result. It doesn't stop at breakpoints.
What do I do to debug a x64 c++ application?
Edit 1
Just found that the debugger says:
Symbol loading for myapp.exe was skipped because it is not specified in the includes modules
What that means?
After checking project and build configuration, I found that the Generate debug info in debug part of linker
(Linker ->Debug: generate debug info)
is blank.
After setting it to yes, the debugger starts to work!