One of the guys here is having a problem with windbg 6.3.0017.0. We just
set him up with a debugging system. He has a local cache for MS’s symbol
server. windbg is connected to the debugging target via serial.
When he’s connected to the target he gets a lot of int3 breaks where the top
of the stack is:
nt!DebugService2+0xe
nt!DebugLoadImageSymbols+0x40
This sheer number of times the debugger breaks here makes it very difficult
to get anywhere while debugging.
Looking through the docs and online I don’t see any reference to similar
problems. Also looking through the docs I don’t see a way to disable
stopping on an int3 breakpoint.
Can anyone suggest why this is breaking in DebugService? Alternatively is
there a way to skip breaking at this int3 in the future so that we can
actually get somewhere while debugging.
-rr
–
Robert Reay
Senior Software Engineer
Belkin Corporation
Research and Development
585-324-7818
585-292-6273 fax www.belkin.comhttp:</http:>
There’s probably a better way to approach this particular problem, but you
can clobber an int 3 with “eb eip 0x90” - assuming you’re still at the
breakpoint, of course. This overwrites the int 3 with a nop. And don’t try
this on an Itanium…
-----Original Message-----
From: Robert Reay [mailto:xxxxx@belkin.com]
Sent: Friday, June 18, 2004 1:31 PM
To: Kernel Debugging Interest List
Cc: Bruce Ramsland
Subject: [windbg] Many int3 breaks
One of the guys here is having a problem with windbg 6.3.0017.0. We just
set him up with a debugging system. He has a local cache for MS’s symbol
server. windbg is connected to the debugging target via serial.
When he’s connected to the target he gets a lot of int3 breaks where the top
of the stack is:
nt!DebugService2+0xe
nt!DebugLoadImageSymbols+0x40
This sheer number of times the debugger breaks here makes it very difficult
to get anywhere while debugging.
Looking through the docs and online I don’t see any reference to similar
problems. Also looking through the docs I don’t see a way to disable
stopping on an int3 breakpoint.
Can anyone suggest why this is breaking in DebugService? Alternatively is
there a way to skip breaking at this int3 in the future so that we can
actually get somewhere while debugging.
-rr
–
Robert Reay
Senior Software Engineer
Belkin Corporation
Research and Development
585-324-7818
585-292-6273 fax www.belkin.comhttp:</http:>
Check your “Debug->Event Filters” dialog and see what the settings for “Load
module” are.
I think if you’ve somehow gotten Execution set to “Enabled” you’ll get
exactly this behaviour. If it isn’t already, try setting it to Output (or
Ignore).
“Robert Reay” wrote in message news:xxxxx@windbg… One of the guys here is having a problem with windbg 6.3.0017.0. We just set him up with a debugging system. He has a local cache for MS’s symbol server. windbg is connected to the debugging target via serial.
When he’s connected to the target he gets a lot of int3 breaks where the top of the stack is: nt!DebugService2+0xe nt!DebugLoadImageSymbols+0x40
This sheer number of times the debugger breaks here makes it very difficult to get anywhere while debugging.
Looking through the docs and online I don’t see any reference to similar problems. Also looking through the docs I don’t see a way to disable stopping on an int3 breakpoint.
Can anyone suggest why this is breaking in DebugService? Alternatively is there a way to skip breaking at this int3 in the future so that we can actually get somewhere while debugging.
-rr
– Robert Reay Senior Software Engineer
Belkin Corporation Research and Development 585-324-7818 585-292-6273 fax www.belkin.com