I am trying to debug my app, which was compiled for 32-bit, native code, under VS2005. It crashes on a Windows 7 64-bit machine. I can't figure out how to get a call stack to see where it's crashing. I installed VS2005 on the Windows 7 machine, ran my app, got my crash -- and the dialog had a "Debug" button on it! Yay! I hit the "Debug" button, and it didn't do anything. How do I need to configure this?
I was wondering if I have to be running a Debug build? I copied my debug binaries over, but they won't run because of "side-by-side configuration" problem; apparently it does not have the debug ATL, MFC, CRT stuff that my 32-bit app wants to use. How do I fix that?
If the debugger won't start after the crash, just attach the debugger before the crash (if possible):
Start the debugger
Choose "Attach to process"
And select your process
The process will possibly hang for a few seconds while the debugger loads all the symbol information.
If your application now crashes, the debugger will automatically stop at the place of the crash. If this doesn't happen, check the Exceptions dialog and enable the relevant exceptions.
When installing VS with defaults, it will not install the 64 bit debugger. You must go back to the installer, select a custom install, and expressly select the 64 bit debugger.
Related
I am trying to run my visual studio (2010) C++ project on an old Windows XP machine that is running VS2010. However, when I run it, I get the error listed in the title of this question. Why is this, and how can I fix it?
Same error was throwing for me when I had Silverlight debugger enabled. To resolve this issue
Open project properties
Under web tab look for Debuggers
Remove the tick mark on "Silverlight"
In general, a debugger should be the same bitness as the debuggee (or at least it must be able to understand the architecture of the target). In any common siutation, an x86-based debugger will not be able to debug an x64 application.
The Visual Studio documentation says:
To debug a 64-bit application that is running on a remote computer,
you need to install the 64-bit remote debugger on the remote computer.
The 64-bit remote debugger is available on the last disc of your
Visual Studio installation set.
I have a VB6 app that loads initially (for a small prompt to enter a license key, only on the first time). It works fine on my machine (windows 7).
I had complaints of it crashing on someone else's machine (both xp and 7), so I made a Windows XP virtual machine. I installed it on the virtual machine, it crashed. I wanted to see where it crashed so I installed Visual Studio on the virtual machine so that I would get a debug prompt. When I ran the program again, it worked.
I am more familiar with C++ and had these kinds of problems, so I figured it was some sort of runtime issue.
I found this VB6 SP6 Redistributable Runtime:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24417
I installed that, and it still wouldn't run.
Any ideas where to go from here?
Edit:
I have tried depends.exe, it only shows MSJava, which I've heard I can ignore. Does depends.exe also show things like .ocx (Active X controllers?) that are required?
Also, from the cmd prompt, %errorlevel% doesn't seem to get populated. Is that a VB6 things, or does that indicate that this is truely a crash and not a user exit?
Open the Visual Basic project and check both "References" and "Components" under the "Project" menu.
Since it is crashing with the VB runtime installed it is likely a component that you have referenced in the project that either does not exist (or is not registered) on the client under test.
This should be a simple fix.
I had the same problem on my windows 7 computer.
I have uninstalled everything, changed my windows theme to Windows Classic.
I changed following properties of VB setup file.
Right click on setup.exe and go to properties and in compatibility tab change the compatibility mode to windows XP SP2. And in settings uncheck the following check boxes.
Disable Visual themes
Disable Desktop composition
Disable display scaling on high DPI settings.
Run this program as an administrator
And have completed installation.
Followed by installing VB 6 service pack 6 from here.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=24417
Hope it helps.
It may require something else other than just the runtime, have you tried viewing it with dependency walker http://www.dependencywalker.com/ on the machine that it crashes on?
It should quickly point out any missing references.
Maybe try again, create a new VM, but install the remote debugger instead of the full VS.
You should create an installer for your application. There may be more dependencies than just the VB6 runtime. A good installation tool will detect at least some of necessary dependencies for you. Have a look at this question or this question
I have a nunit DLL written in c++ and build for framework 4 for an x64 processor. I have nunit set up as my launch exe for debugging. From my understanding VS starts the remote debugger when having to debug x64 applications. For the last day or so the remote debugger monitor is crashing sporadically which is annoying. I have checked the event logs and there is no information other than a guid. If I could just restart the msvsmon.exe and restart debugging it would be on thing, but if I fire one up VS can't attach to it.
Any one have any clues as why msvsmon would start crashing.
Is there a way to force VS to reattach to a new instance.
When running the debugger about 50% of the time, Visual Studio 2010 freezes and also locks up my entire machine. I can't even get to Task Manager. Nothing works except my mouse will still move. The only way to recover is to hard boot the machine which takes about 15 minutes each time. I don't have anything else running on my machine at the time except VS, IE 8 (sometimes) and Outlook.
I am running Windows XP on a Lenovo T400 with 3G RAM
Has anyone seen this behavior? If so, how did you fix it?
Thanks,
Rhonda
You don't mention what language your app is but I have run into this with our C++/CLI application on occasion. To avoid it, I changed the Project properties / Debugger and specify "Native" or "Managed" explicitly for the debugger type. The default of "Auto" can get confused.
Also, if you use Application Verifier from Microsoft, I have had VS hang while AV was configured to verify our .exe. To avoid this, we have to launch the app under the debugger as "Native".
Recently, my coworker and I upgraded our development environment to Win7 x64 with VS2010 Pro. Our application is specifically targeted at x64 platform.
The problem we are encountering is during debugging, when attempting to step through the code (F10), at least 50% of the time VS will simply lock up the application being debugged. The IDE has the appearance of having pressed F5, but the application is not responsive and we have to force stop the application.
Our application is a Client (GUI) and a Server that communicate through .NET remoting.
This is starting to directly affect our productivity, so if anyone has any ideas what may be causing this, please let me know.
There is an outside chance that it might be the debug symbols loading. Check the status bar I think it tells you when the symbols are loading.
This may be a moot point, but have you installed the VS 2010 service pack 1?
There are various bugfixes related to debuggers included.
http://support.microsoft.com/kb/983509
I had a similar problem. it turned out that a higher level program had a different run-time library (multi-threaded debug dll), while my app was simply a multi-threaded debug. Once I converted mine to a multi-threaded debug dll, the freeze stopped happening.