Headless debugging on Windows
There is a bug that I would like to fix that only occurs on Windows Server without a GUI running. I have set up a Windows Server 2019 machine on Google Compute Engine that reproduces the bug, and would like to debug it.
Ideally, I would like to use gdb, but seeing as the program was built with Visual Studio 2019, gdb can't read the debugging symbols.
I don't have a Windows machine, so using Visual Studio will be difficult. I could set up a VM, but if there's an in-terminal way to do this that would be preferred.
I did a pretty thorough Google search, but it didn't turn up anything. Is there really no Windows solution for debugging C++ code headlessly?
MS has 2 console debuggers called CDB and NTSD so you don't actually need Visual Studio GUI to do the debugging. In fact there are a lot of debugging environments in Windows from MS beside the usual Visual Studio. Just install them in your Windows Server and control them remotely from your terminal
You can also debug MSVC-compiled code with LLDB since the PDB format has been published long time ago and LLVM on Windows does support it. No idea about current LLDB on Linux though
And since you have the source code, sometimes the old-school printf debugger is the best way to analyze the issue
If you can get a Windows VM it'll be much better to do remote debugging. In fact almost all debuggers support that feature including GDB or LLDB, so even if you don't have the source code you can still run any Windows debugger and step through the instructions instead of high-level code lines from a remote machine
An alternative way is to take a memory dump and debug later. After getting the dump file, just drag it into your VS solution or any debugging tool like WinDbg and then select "Start Debugging". Now you can step through instructions/code lines and examine variables' values, or jump to an arbitrary function's stack frame just as if you're really running the malfunctioning app
There are many ways to dump a process' memory. You can set Windows to automatically save a dump file when your app crashes, or just capture memory snapshots manually during runtime. Comparing 2 snapshots is also useful for detecting leaked memory. For more information on how to do that read
There's also an easy way to take a dump of a live process using task manager (or any other similar tools)
- What is the fastest way to swap values in C?
- What's the best way to do a lookup table in C?
- Why use print("%s", "string") and not just only print("string")?
- Getting HWND of current Process
- Is there a systemd-independent function for getting a USB device model?
- How can i add line breaks when rendering Text using X11,
- Two different times in C
- How does Boehm's Garbage Collector free memory without creating a separate thread for the GC?
- I run into a about rvalue concept problem in C Programming Language
- This is a C program meant to run the string characters in the array
- _Atomic struct assignment of arbitrary size in C?
- Get home directory in Linux
- Detecting Endianness
- How do I get a hexadecimal string representation of a GdkRGBA struct in C?
- How is the conditional operator parsed?
- Why an integer has different value even when its position is not changed
- In C, is it true that PRId64 is defined if-and-only-if int64_t is available?
- Poor performance of check library, when using assertions
- Is there any way to flash a raspberry Pi Pico with a firmware contained in a pointer inside it?
- Concatenating command line arguments
- Best practices for circular shift (rotate) operations in C++
- Static build of GMP for MSVC (Windows)
- How to build GMP in MSYS2?
- tun program not creating device node
- C parameter pass by value when parameter is a structure. Can we ensure at least the single parameter is atomic?
- Time complexity in Divide and Conquer algorithms
- Compute fast log base 2 ceiling
- How to convert an OpenCV cv::Mat into a float* that can be fed into Vlfeat vl_dsift_process ?
- Are different translation units allowed to define structures with the same name?
- What is the difference between terminating a program with Ctrl+d and Ctrl+c when writing to txt file