I've seen the same question in the link below but somehow it didn't work for me.
x86 Remote Debugger Service on x64
when I'm running the MSVSMON.EXE - X86 i'm getting in the visual studio this error:
and when I'm running the x64 version of MSVSMON.EXE it shows:
Related
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
I'm developing a program in C++ and I'm facing a problem. When I run it on my development (Win 10) machine, it works fine. As it also has to run on Windows XP, I installed Windows XP in VMWare and tried to run it, but it crashes. It's been compiled with the latest Visual Studio toolset for Windows XP, so this is not the problem. There's not much info about the crash on the machine.
How do I debug it remotely? I'll probably need to attach it to Visual Studio 2015s debugger, but if there's another solution, I won't be against it.
You can install Visual Studio Remote Debugger on a machine that has problems and connect to it from your Visual Studio. After that you will be able to debug a remote process from your PC.
The latest remote debugger support Windows 7 and newer, so you might end up installing older version from VS 2013 or 2010 that would support Windows XP.
I am unable to launch my application on Windows Server 2008 R2 x64. It was built via Visual Studio 2013 (toolset -- v120_xp, static linkage with CRT). On other systems (for example, Windows 8 x64 and Windows 7 x64) application works as expected, while on Windows Server 2008 R2 x64 it gives me the following error:
When I try to run this application via WinDbg it shows this error right after the following line:
ModLoad: 00000000007b0000 000000000094a000
C:\Users\Administrator\Desktop\app\LIBEAY32.dll
I've tried to download x64 OpenSSL binaries and replace the "libeay32.dll" and "ssleay32.dll" files in the application's directory, but it gives me the same error.
Yes, there are a lot of questions about similar errors, but unfortunately I didn't find any answer for my case.
What am I doing wrong? How can I fix it?
Thanks in advance.
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!
I have a Win32 C++ Application using a handful of third-Party DLLs that is installed at some hundred costumer machines. I recently tested the x86 Version of the installation successfully on Windows XP, Windows Vista x64, Windows 7 x86 as well as Windows Server 2008 x86. No Problems. The Installer (nullsoft) installs the redistributable files for VC 2005 and VC 2008 as both are required by different DLLs we use.
But with Windows Server 2008 x64 both, the x86 and the x64 Versions refuse to start.
When i start the x86 Version of the program a Dialog appears:
<myApp> has stopped Working.
The EventLog contains a message:
Faulting application myapp.exe, version 1.0.0.0, time stamp 0x4bcb37ca,
faulting module MSVCR80.dll, version 8.0.50727.4053, time stamp 0x4a594c79,
exception code 0xc000000d, fault offset 0x0001ce0b, process id 0x29c,
application start time 0x01cb0329976cfc68.
\Windows\winsxs contains a directory
x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d08d7da0442a985d
Using sxstrace (first trace, then parse) a log file of 3 Bytes length is created containing non readable characters. Behavior of the x64 Version is similar. Also all demo programms from the 3rd Party Dlls are working properly. Any hint ?
It doesn't look like a side-by-side error. The exception code is STATUS_INVALID_PARAMETER, "An invalid parameter was passed to a service or function." That doesn't help. You'll need a debugger, probably with the Windows debugging symbols. Make it stop on the first-chance exception.