Making a kernel breakpoint a bit more convenient

WINDBG
1

I just discovered a neat capability that I think has been lurking in
Windbg for a long time, but undiscovered by me. I’ve always found it kind
of inconvenient to use DbgBreakPoint/KdBreakPoint, because you end up in
the DbgBreakPoint function in the debugger, not the function that called
it. Today I discovered that I could add the command “gu” (which is the
command line version of Step Out) to the Break instruction exception Event
Filter, and that will step back out to the DbgBreakPoint callsite, which
was exactly where I really wanted to be.

Thanks, Windbg team!

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842

2

wrote in message news:xxxxx@windbg…
> I’ve always found it kind
> of inconvenient to use DbgBreakPoint/KdBreakPoint, because you end up in
> the DbgBreakPoint function in the debugger, not the function that called

Intrinsic function __debugbreak will stop exactly where you put it.

Regards,
–PA

3

Wow, didn’t know about that one. Mind if I blog about this week ?

Thx
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Sunday, May 07, 2006 6:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Making a kernel breakpoint a bit more convenient

wrote in message news:xxxxx@windbg…
> I’ve always found it kind
> of inconvenient to use DbgBreakPoint/KdBreakPoint, because you end up
in
> the DbgBreakPoint function in the debugger, not the function that
called

Intrinsic function __debugbreak will stop exactly where you put it.

Regards,
–PA

—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Sure, Doron, you’re very welcome
– PA

“Doron Holan” wrote in message news:xxxxx@windbg…
Wow, didn’t know about that one. Mind if I blog about this week ?

Thx
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Sunday, May 07, 2006 6:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Making a kernel breakpoint a bit more convenient

wrote in message news:xxxxx@windbg…
> I’ve always found it kind
> of inconvenient to use DbgBreakPoint/KdBreakPoint, because you end up
in
> the DbgBreakPoint function in the debugger, not the function that
called

Intrinsic function __debugbreak will stop exactly where you put it.

Regards,
–PA

—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

For those who want to read it

http://blogs.msdn.com/doronh/archive/2006/05/08/592735.aspx

d

– I can spell, I just can’t type.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Friday, May 12, 2006 1:11 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Making a kernel breakpoint a bit more convenient

Sure, Doron, you’re very welcome
– PA

“Doron Holan” wrote in message
news:xxxxx@windbg…
Wow, didn’t know about that one. Mind if I blog about this week ?

Thx
d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel A.
Sent: Sunday, May 07, 2006 6:13 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Making a kernel breakpoint a bit more convenient

wrote in message news:xxxxx@windbg…
> I’ve always found it kind
> of inconvenient to use DbgBreakPoint/KdBreakPoint, because you end up
in
> the DbgBreakPoint function in the debugger, not the function that
called

Intrinsic function __debugbreak will stop exactly where you put it.

Regards,
–PA

—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com