Re: Windbg: Disable user mode debugging
- From: "Armin Zingler" <az.nospam@xxxxxxxxxx>
- Date: Thu, 10 Jan 2008 02:57:06 +0100
"David Craig" <drivers@xxxxxxxxxx> schrieb
This is really the wrong group for windbg.
Sorry, I did not even suspect there's an extra windbg group. Thanks.
But maybe it's not the right group, too (see below).
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.
I see.
Use 1394a with a TI chipset and the speed
problem is mostly solved.
I shouldn't have a speed problem with the current connection. That's
the point. I just want to run VS on the target computer. I don't
see why it slows the machine down because everything else I do
does not do it.
The problem is the combination VS+active kernel debugger. That's why
it is hard to limit the question to only one group. I don't think
m.p.windbg is the right place because it's only a problem on the
target machine where, as you wrote above, the "special kernel mode DLLs"
reside and where also VS runs.
I've already asked in the (German) VS group meanwhile, but I also
think that this group is the right one because of the "kernel debugging"
component. (I didn't find another "kernel" group @ m.p)
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.
Ok
BTW, kdbgctrl.exe (on the target machine) always tells me:
"Unable to get Kernel debugger user exception enable, NTSTATUS 0xC0000003"
Don't worry, I'll handle it....
Armin
"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
> >
> >
>
.
- Follow-Ups:
- Re: Windbg: Disable user mode debugging
- From: David Craig
- Re: Windbg: Disable user mode debugging
- References:
- Windbg: Disable user mode debugging
- From: Armin Zingler
- Re: Windbg: Disable user mode debugging
- From: Armin Zingler
- Re: Windbg: Disable user mode debugging
- From: Ivan Brugiolo [MSFT]
- Re: Windbg: Disable user mode debugging
- From: Armin Zingler
- Re: Windbg: Disable user mode debugging
- From: David Craig
- 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):
Relevant Pages
|
