Re: Windbg: Disable user mode debugging

This is really the wrong group for windbg. However, the kernel debugger is
in special kernel mode DLLs on the target system where boot.ini or the
bootcfg files reside. Windbg is NOT a kernel debugger, but a user mode
interface to the kernel debugger running on the target system. Use 1394a
with a TI chipset and the speed problem is mostly solved. SMP is always
slower than UP because the kernel debugger must marshal all the CPUs each
time it breaks. Single stepping is much slower on SMP than UP.

"Armin Zingler" <az.nospam@xxxxxxxxxx> wrote in message
news:ODka4rxUIHA.5816@xxxxxxxxxxxxxxxxxxxxxxx
Ivan, thanks again for your fast response.

"Ivan Brugiolo [MSFT]" <ivanbrug@xxxxxxxxxxxxxxxxxxxx> schrieb
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`.

This "enables kernel debugger user exception handling".
I want to disable it. That's why I used "/debug=noumex" in boot.ini.
I want VS to handle user mode exceptions. Sorry if I wasn't clear
enough:

PC #1: a) BSOD machine b) boot.ini: "/debug=noumex" c) Runs VS (slowly)
I want to run VS here just like I always did. Without the
mentioned warning message and without slowing down the machine.

PC #2: runs Windbg (no problem here)

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.

It is not a general slow-down. Only when VS is running, so the following
only applies after starting VS:

- Without "/debug=noumex": Windbg (on PC #2) frequently stops
at 80000003 exceptions. I can continue every time but it immediatelly
stops again.

- With "/debug=noumex": Windbg ignores 80000003 exceptions as intended.
But: slow-down of PC #1. I don't know why. Like you, I also guessed
that there is still (slow serial) data exchange, but I don't know why
and how to solve it.


I really wonder what they meant by saying "The kernel debugger can be
configured to allow debugging in Visual Studio". The kernel debugger is
Windbg on PC #2, but how to configure it...?


Armin


--

--
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





.

Relevant Pages

  • Re: Windbg: Disable user mode debugging
    ... subsystem runs is the place where the kernel debugger runs. ... I know the windbg group has people from Microsoft ... on the target system. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Windbg: Disable user mode debugging
    ... the win32 subsystem runs is the place where the kernel debugger runs. ... Suggestion 3 "In the Kernel Debugger, disable user-mode exceptions." ... on the target system. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Serial Out from Kernel Mode
    ... > The problem is that the target audience for such a driver has very ... > question.Cuz if they have the use the Windbg then they need to place ... >>> I need to pass the debug statements from a kernel driver thru the ... >> Stop trying to re-implement the kernel debugger. ...
    (microsoft.public.win32.programmer.kernel)
  • RE: NDIS IM - strange installation
    ... for no reason. ... Attach a kernel debugger (e.g. WinDbg) and make sure it's connected (you ...
    (microsoft.public.development.device.drivers)
  • Re: Serial Out from Kernel Mode
    ... > The problem is that the target audience for such a driver has very ... > question.Cuz if they have the use the Windbg then they need to place ... >>> I need to pass the debug statements from a kernel driver thru the ... >> Stop trying to re-implement the kernel debugger. ...
    (microsoft.public.development.device.drivers)
Loading