I added my C++ application to Application Verifier. I am able to run it by directly executing the exe. But if I run it from VS 2013 or WinDbg, it just hangs with 0 CPU usage.
Even if I directly execute the exe, at a certain point it uses all my memory (10GB), and I have to restart the computer. So now I do not have a way to use Application Verifier to debug it.
There is only one line log created when my application starts. I do not see any other logs in Application Verifier.
Does anyone know what is wrong with my case?
If I disable the TLS option in Application Verifier, it will work in a debugger.
Related
Because of the possibility of full system failure, I am using VM's as the environment for debugging a system startup component like "userinit", which executes before the desktop appears. How do I configure the VM's remote debugger and system so I can debug from the first line of code?
Look here:
Setting Up Kernel-Mode Debugging Manually
I am able to run my web application on the remote machine (after logging into VM using VPN) without debug but when I try to attach the process I don't find application process to attach for debugging even after I checking the option of show processes from all users.
If I try to start application with debug dotnet.exe crashes immediately, I believe this problem is due to VPN which is blocking the process but not sure how to fix it.
I'm running into heap corruption with an application I'm developing, so I tried using Application Verifier to track it down, but now I can't seem to remove Application Verifier.
Running the original program loads the verifier automatically, removing it from application verifier or uninstalling application verifier didn't help.
The registry keys are my one lead, however I'm unsure what to do with them.
Solved, I had an application verifier as a part of the Windows SDK, as well as a standalone version. Another possible cause was I made sure I clicked 'save' after removing my application from the Application Verifier list.
Im using this guide "automating the testing of windows 8 apps" to test my windows store app
http://blogs.msdn.com/b/windowsappdev/archive/2012/09/04/automating-the-testing-of-windows-8-apps.aspx
Unfortunaltely Ive run into a problem, I need to know when my app closes (crashes) or when it goes into suspended mode, to log that info, and I want the launcher to be able to know the application has stopped , unfortunately iApplicationActionManager, does not have that method. And IPackageDebugSettings which is used to change the application suspend and resume states does not have a readable current state property (afaik)
Is there any way to do this?
I'm writing an SNMP extension agent DLL for Windows.
Is there a way to automatically attach the DLL to the SNMP service each time I want to test/debug?
This is a very tedious and time consuming process, as I currently have to stop the SNMP service, compile, restart the service and then attach the process. I'm trying to automate it more.
This may be what you want to have a look at.
Visual Studio debugger offers some command line option to attach to running process. You can probably write a Python script to enumerate running processes and attach the debugger to the service. I think you need admin priviledge to do that.
.Net has a convinient Debugger.Launch(), but I can't find an equivalent for the native.