control-c break equivalent

WINDBG
1

sometimes I mistype symbols and then have to wait long time while windbg try to find unfindable thing. There is way to break out of *BUSY* status?

BA

2

Control-break or II button in windbg.
–pa

wrote in message news:xxxxx@windbg…
> sometimes I mistype symbols and then have to wait long time while windbg
> try to find unfindable thing. There is way to break out of BUSY status?
>
> BA
>

3

You could also tell windbg to require qualified symbol names, which means
that you’ll need to qualify each symbol with the module name (MODULE!SYMBOL)
by setting the symbol options (see .symopt). This will limit the search
scope and prevent windbg going off into the weeds.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Wednesday, August 25, 2010 9:53 PM
To: Kernel Debugging Interest List
Subject: [windbg] control-c break equivalent

sometimes I mistype symbols and then have to wait long time while windbg try
to find unfindable thing. There is way to break out of *BUSY* status?

BA

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

4

Pavel, that doesn’t work. In windbg, open disassembly window. Put in “bla” and it spins. break and pause don’t stop the *BUSY*.

BA

5

Mr. Man, I think I will use .symopt for future. That will help with symbols, but prob not other things, but symbols are the problem for me most of the time. Thanks

6

Not a problem.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Wednesday, August 25, 2010 10:57 PM
To: Kernel Debugging Interest List
Subject: RE:[windbg] control-c break equivalent

Mr. Man, I think I will use .symopt for future. That will help with symbols,
but prob not other things, but symbols are the problem for me most of the
time. Thanks

WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

7

Hold down control and keep hitting break. Sometimes it takes quite a bit of
whacking break, try getting angry with it and see if that makes it stop.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
> Pavel, that doesn’t work. In windbg, open disassembly window. Put in “bla”
> and it spins. break and pause don’t stop the BUSY.
>
> BA
>

8

Hmmmm … I think by anger Scott means the number of repetitive strikes, NOT
the force with which you strike. A broken keyboard will do nothing to get
WinDbg’s attention. Well, I suppose Murphy would state that as soon as you
do break the keyboard, WinDbg WILL break, which will do you no good since
you just broke the keyboard.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 6:51 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Hold down control and keep hitting break. Sometimes it takes quite a bit of
whacking break, try getting angry with it and see if that makes it stop.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
> Pavel, that doesn’t work. In windbg, open disassembly window. Put in “bla”

> and it spins. break and pause don’t stop the BUSY.
>
> BA
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

9

Treat it like the walk signal button. I’m not always convinced that those
actually do anything, but at least they give you something to do while you
wait for the light to change (or, in this case, for WinDBG to stop).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Gary G. Little” wrote in message
news:xxxxx@windbg…
> Hmmmm … I think by anger Scott means the number of repetitive strikes,
> NOT
> the force with which you strike. A broken keyboard will do nothing to get
> WinDbg’s attention. Well, I suppose Murphy would state that as soon as you
> do break the keyboard, WinDbg WILL break, which will do you no good since
> you just broke the keyboard.
>
> Gary G. Little
> H (952) 223-1349
> C (952) 454-4629
> xxxxx@comcast.net
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 6:51 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Hold down control and keep hitting break. Sometimes it takes quite a bit
> of
> whacking break, try getting angry with it and see if that makes it stop.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>> “bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

10

Sometimes you really do have to ctrl-break several times, although I consider this a bug in the extension in question (and one of my pet peeves). This happens when there may be several layers of debugger extension code running; the uppermost might notice the user interrupt event (i.e. ctrl-break) and stop processing, but not correctly propagate it up to the previous layer (which might continue on with whatever loop it was running). Because delivery of the user interrupt unsets the interrupt code, not breaking out all the way can cause a necessity to issue multiple ctrl-break’s to really stop whatever processing is going on.

If you are writing a debugger extension, you can be a good citizen by making sure that if you’re nested several levels deep, you break out all the way on the first debugger user interrupt event you receive. Engextcpp has a nice C++ exception-based framework for doing this.

If you’re writing a utility extension that is invoked by another extension, it might be appropriate to re-raise the interrupt once you handle it via IDebugControl::SetInterrupt.

  • S

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 7:12 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Treat it like the walk signal button. I’m not always convinced that those actually do anything, but at least they give you something to do while you wait for the light to change (or, in this case, for WinDBG to stop).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Gary G. Little” wrote in message
news:xxxxx@windbg…
> Hmmmm … I think by anger Scott means the number of repetitive strikes,
> NOT
> the force with which you strike. A broken keyboard will do nothing to get
> WinDbg’s attention. Well, I suppose Murphy would state that as soon as you
> do break the keyboard, WinDbg WILL break, which will do you no good since
> you just broke the keyboard.
>
> Gary G. Little
> H (952) 223-1349
> C (952) 454-4629
> xxxxx@comcast.net
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 6:51 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Hold down control and keep hitting break. Sometimes it takes quite a bit
> of
> whacking break, try getting angry with it and see if that makes it stop.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>> “bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

11

“Skywing” wrote in message
news:xxxxx@windbg…
>Sometimes you really do have to ctrl-break several times, although I
>consider this a bug in the extension in question (and one >of my pet
>peeves). This happens when there may be several layers of debugger
>extension code running; the uppermost might >notice the user interrupt
>event (i.e. ctrl-break) and stop processing, but not correctly propagate it
>up to the previous layer

!for_each_process and !for_each_thread are extreme examples of this, once
they get going there’s no stopping them from trying to execute the given
command for every process/thread (and oh have I tried).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Skywing” wrote in message
news:xxxxx@windbg…
> Sometimes you really do have to ctrl-break several times, although I
> consider this a bug in the extension in question (and one of my pet
> peeves). This happens when there may be several layers of debugger
> extension code running; the uppermost might notice the user interrupt
> event (i.e. ctrl-break) and stop processing, but not correctly propagate
> it up to the previous layer (which might continue on with whatever loop it
> was running). Because delivery of the user interrupt unsets the interrupt
> code, not breaking out all the way can cause a necessity to issue multiple
> ctrl-break’s to really stop whatever processing is going on.
>
> If you are writing a debugger extension, you can be a good citizen by
> making sure that if you’re nested several levels deep, you break out all
> the way on the first debugger user interrupt event you receive. Engextcpp
> has a nice C++ exception-based framework for doing this.
>
> If you’re writing a utility extension that is invoked by another
> extension, it might be appropriate to re-raise the interrupt once you
> handle it via IDebugControl::SetInterrupt.
>
> - S
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 7:12 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Treat it like the walk signal button. I’m not always convinced that those
> actually do anything, but at least they give you something to do while you
> wait for the light to change (or, in this case, for WinDBG to stop).
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> “Gary G. Little” wrote in message
> news:xxxxx@windbg…
>> Hmmmm … I think by anger Scott means the number of repetitive strikes,
>> NOT
>> the force with which you strike. A broken keyboard will do nothing to get
>> WinDbg’s attention. Well, I suppose Murphy would state that as soon as
>> you
>> do break the keyboard, WinDbg WILL break, which will do you no good since
>> you just broke the keyboard.
>>
>> Gary G. Little
>> H (952) 223-1349
>> C (952) 454-4629
>> xxxxx@comcast.net
>>
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
>> Sent: Thursday, August 26, 2010 6:51 AM
>> To: Kernel Debugging Interest List
>> Subject: Re:[windbg] control-c break equivalent
>>
>> Hold down control and keep hitting break. Sometimes it takes quite a bit
>> of
>> whacking break, try getting angry with it and see if that makes it stop.
>>
>> -scott
>>
>> –
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>>
>>
>> wrote in message news:xxxxx@windbg…
>>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>>> “bla”
>>
>>> and it spins. break and pause don’t stop the BUSY.
>>>
>>> BA
>>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

12

Although presumably not related, I find this to be true for the hypervisor
debugger as well.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 3:36 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Re:control-c break equivalent

“Skywing” wrote in message
news:xxxxx@windbg…
>Sometimes you really do have to ctrl-break several times, although I
>consider this a bug in the extension in question (and one >of my pet
>peeves). This happens when there may be several layers of debugger
>extension code running; the uppermost might >notice the user interrupt
>event (i.e. ctrl-break) and stop processing, but not correctly
>propagate it up to the previous layer

!for_each_process and !for_each_thread are extreme examples of this, once
they get going there’s no stopping them from trying to execute the given
command for every process/thread (and oh have I tried).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Skywing” wrote in message
news:xxxxx@windbg…
> Sometimes you really do have to ctrl-break several times, although I
> consider this a bug in the extension in question (and one of my pet
> peeves). This happens when there may be several layers of debugger
> extension code running; the uppermost might notice the user interrupt
> event (i.e. ctrl-break) and stop processing, but not correctly propagate
> it up to the previous layer (which might continue on with whatever loop it

> was running). Because delivery of the user interrupt unsets the interrupt

> code, not breaking out all the way can cause a necessity to issue multiple

> ctrl-break’s to really stop whatever processing is going on.
>
> If you are writing a debugger extension, you can be a good citizen by
> making sure that if you’re nested several levels deep, you break out all
> the way on the first debugger user interrupt event you receive. Engextcpp

> has a nice C++ exception-based framework for doing this.
>
> If you’re writing a utility extension that is invoked by another
> extension, it might be appropriate to re-raise the interrupt once you
> handle it via IDebugControl::SetInterrupt.
>
> - S
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 7:12 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Treat it like the walk signal button. I’m not always convinced that those
> actually do anything, but at least they give you something to do while you

> wait for the light to change (or, in this case, for WinDBG to stop).
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> “Gary G. Little” wrote in message
> news:xxxxx@windbg…
>> Hmmmm … I think by anger Scott means the number of repetitive strikes,
>> NOT
>> the force with which you strike. A broken keyboard will do nothing to get
>> WinDbg’s attention. Well, I suppose Murphy would state that as soon as
>> you
>> do break the keyboard, WinDbg WILL break, which will do you no good since
>> you just broke the keyboard.
>>
>> Gary G. Little
>> H (952) 223-1349
>> C (952) 454-4629
>> xxxxx@comcast.net
>>
>>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
>> Sent: Thursday, August 26, 2010 6:51 AM
>> To: Kernel Debugging Interest List
>> Subject: Re:[windbg] control-c break equivalent
>>
>> Hold down control and keep hitting break. Sometimes it takes quite a bit
>> of
>> whacking break, try getting angry with it and see if that makes it stop.
>>
>> -scott
>>
>> –
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>>
>>
>> wrote in message news:xxxxx@windbg…
>>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>>> “bla”
>>
>>> and it spins. break and pause don’t stop the BUSY.
>>>
>>> BA
>>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

13

EngExtCpp is nice all around, I think.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Thursday, August 26, 2010 3:02 PM
To: Kernel Debugging Interest List
Subject: RE: Re:[windbg] control-c break equivalent

Sometimes you really do have to ctrl-break several times, although I
consider this a bug in the extension in question (and one of my pet peeves).
This happens when there may be several layers of debugger extension code
running; the uppermost might notice the user interrupt event (i.e.
ctrl-break) and stop processing, but not correctly propagate it up to the
previous layer (which might continue on with whatever loop it was running).
Because delivery of the user interrupt unsets the interrupt code, not
breaking out all the way can cause a necessity to issue multiple
ctrl-break’s to really stop whatever processing is going on.

If you are writing a debugger extension, you can be a good citizen by making
sure that if you’re nested several levels deep, you break out all the way on
the first debugger user interrupt event you receive. Engextcpp has a nice
C++ exception-based framework for doing this.

If you’re writing a utility extension that is invoked by another extension,
it might be appropriate to re-raise the interrupt once you handle it via
IDebugControl::SetInterrupt.

  • S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 7:12 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Treat it like the walk signal button. I’m not always convinced that those
actually do anything, but at least they give you something to do while you
wait for the light to change (or, in this case, for WinDBG to stop).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Gary G. Little” wrote in message
news:xxxxx@windbg…
> Hmmmm … I think by anger Scott means the number of repetitive
> strikes, NOT the force with which you strike. A broken keyboard will
> do nothing to get WinDbg’s attention. Well, I suppose Murphy would
> state that as soon as you do break the keyboard, WinDbg WILL break,
> which will do you no good since you just broke the keyboard.
>
> Gary G. Little
> H (952) 223-1349
> C (952) 454-4629
> xxxxx@comcast.net
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 6:51 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Hold down control and keep hitting break. Sometimes it takes quite a
> bit of whacking break, try getting angry with it and see if that makes
> it stop.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>> “bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

14

Dry@g

Sent from my Nokia phone
-----Original Message-----
From: M. M. O’Brien
Sent: 27-08-2010 4:17:39 am
Subject: RE: Re:[windbg] control-c break equivalent

EngExtCpp is nice all around, I think.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Skywing
Sent: Thursday, August 26, 2010 3:02 PM
To: Kernel Debugging Interest List
Subject: RE: Re:[windbg] control-c break equivalent

Sometimes you really do have to ctrl-break several times, although I
consider this a bug in the extension in question (and one of my pet peeves).
This happens when there may be several layers of debugger extension code
running; the uppermost might notice the user interrupt event (i.e.
ctrl-break) and stop processing, but not correctly propagate it up to the
previous layer (which might continue on with whatever loop it was running).
Because delivery of the user interrupt unsets the interrupt code, not
breaking out all the way can cause a necessity to issue multiple
ctrl-break’s to really stop whatever processing is going on.

If you are writing a debugger extension, you can be a good citizen by making
sure that if you’re nested several levels deep, you break out all the way on
the first debugger user interrupt event you receive. Engextcpp has a nice
C++ exception-based framework for doing this.

If you’re writing a utility extension that is invoked by another extension,
it might be appropriate to re-raise the interrupt once you handle it via
IDebugControl::SetInterrupt.

  • S

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 7:12 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Treat it like the walk signal button. I’m not always convinced that those
actually do anything, but at least they give you something to do while you
wait for the light to change (or, in this case, for WinDBG to stop).

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Gary G. Little” wrote in message
news:xxxxx@windbg…
> Hmmmm … I think by anger Scott means the number of repetitive
> strikes, NOT the force with which you strike. A broken keyboard will
> do nothing to get WinDbg’s attention. Well, I suppose Murphy would
> state that as soon as you do break the keyboard, WinDbg WILL break,
> which will do you no good since you just broke the keyboard.
>
> Gary G. Little
> H (952) 223-1349
> C (952) 454-4629
> xxxxx@comcast.net
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
> Sent: Thursday, August 26, 2010 6:51 AM
> To: Kernel Debugging Interest List
> Subject: Re:[windbg] control-c break equivalent
>
> Hold down control and keep hitting break. Sometimes it takes quite a
> bit of whacking break, try getting angry with it and see if that makes
> it stop.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
>> “bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

15

When the keyboard reaches its final death throws, you might get lucky as
it might send a keycode or two to the computer that windbg is listening
for. I say go for it. I always keep a ball-peen hammer or wood chipper
nearby for tough debugging assignments, anyway.

.pat styles [microsoft]

Gary G. Little wrote:

Hmmmm … I think by anger Scott means the number of repetitive strikes, NOT
the force with which you strike. A broken keyboard will do nothing to get
WinDbg’s attention. Well, I suppose Murphy would state that as soon as you
do break the keyboard, WinDbg WILL break, which will do you no good since
you just broke the keyboard.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 6:51 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Hold down control and keep hitting break. Sometimes it takes quite a bit of
whacking break, try getting angry with it and see if that makes it stop.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in “bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

16

AHHH … a fellow soul of like mind. I too enjoy a hearty bash with a sledge
hammer of recalcitrant computing devices. The feel of the sledge passing
through the monitor and the sound of a muffled implosion as that stubborn
monitor finally succumbs to a more irresistible force warms my soul. These
new LCD monitors have such an unsatisfying “crunch”. Not nearly as soothing
as a nice CRT.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of pat styles
[microsoft]
Sent: Monday, August 30, 2010 12:27 AM
To: Kernel Debugging Interest List
Cc: ‘Kernel Debugging Interest List’
Subject: Re:[windbg] control-c break equivalent

When the keyboard reaches its final death throws, you might get lucky as it
might send a keycode or two to the computer that windbg is listening for. I
say go for it. I always keep a ball-peen hammer or wood chipper nearby for
tough debugging assignments, anyway.

.pat styles [microsoft]

Gary G. Little wrote:

Hmmmm … I think by anger Scott means the number of repetitive
strikes, NOT the force with which you strike. A broken keyboard will
do nothing to get WinDbg’s attention. Well, I suppose Murphy would
state that as soon as you do break the keyboard, WinDbg WILL break,
which will do you no good since you just broke the keyboard.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Thursday, August 26, 2010 6:51 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] control-c break equivalent

Hold down control and keep hitting break. Sometimes it takes quite a
bit of whacking break, try getting angry with it and see if that makes it
stop.

-scott

–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…
>> Pavel, that doesn’t work. In windbg, open disassembly window. Put in
“bla”
>
>> and it spins. break and pause don’t stop the BUSY.
>>
>> BA
>>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer