Re: Windbg: Disable user mode debugging
- From: "Ivan Brugiolo [MSFT]" <ivanbrug@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 9 Jan 2008 15:07:40 -0800
The warning given by Visual Studio is an artifact/consequence of the way
the managed-code debugging infrastructure was (poorly) designed.
Basically, the managed code debugging infrastructure requires
exeception reflection even when KD is active.
You would need to run `kdbgctrl.exe -eu`.
For the general slow-down of the machine, I cannot speculate.
I run all of my machines with KD enabled all the times, and,
there is no slowdown that I can see.
Maybe there is some debug-spew going on, and, writing to the serial port
is very slow.
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Armin Zingler" <az.nospam@xxxxxxxxxx> wrote in message
news:uLuBvDxUIHA.4196@xxxxxxxxxxxxxxxxxxxxxxx
"Armin Zingler" <az.nospam@xxxxxxxxxx> schrieb
Or, is using the "/crashdebug" option in boot.ini (on the target
computer) the only way to get rid of the VS message?
Ok, I found the boot.ini "/debug=noumex" switch. Sorry for bothering...
But, VS' message is still the same. In addition, the target machine is
really slow (mouse movements only every 5th second). So, there is still
the question how to start VS on the target machine without this message
and without slowdown.
Thanks!
Armin
.
- Follow-Ups:
- Re: Windbg: Disable user mode debugging
- From: Armin Zingler
- Re: Windbg: Disable user mode debugging
- References:
- Windbg: Disable user mode debugging
- From: Armin Zingler
- Re: Windbg: Disable user mode debugging
- From: Armin Zingler
- Windbg: Disable user mode debugging
- Prev by Date: Re: Windbg: Disable user mode debugging
- Next by Date: Re: Windbg: Disable user mode debugging
- Previous by thread: Re: Windbg: Disable user mode debugging
- Next by thread: Re: Windbg: Disable user mode debugging
- Index(es):
Loading