Is this expected behavior?

WINDBG
1

I just got a bugcheck on WinXP while debugging a driver with Windbg 6.0.7.
As expected I got the following message:

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, f5c9e7f5}

Probably caused by : fg8100.sys ( fg8100!cfFg8100DeviceControl+68c )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804f784c cc int 3

I then did the !analyze -v but it immediately returns with “The debuggee is
ready to run”. I know what the cause of my bugcheck since the debugger had
a valid stack trace. Is this the expected behavior when a bugcheck occurs
while single stepping (step over) through the code?

  • Steve -
2

Hi Steve,

I always get the message “The debuggee is ready to run” when doing an
analyze command on a Memory.dmp file. When I connect directly to the
debugee (using a serial 115200 cable connection) this does not happen
and I get all the needed info.

grtx
Marco.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Whitman, Steve
Sent: Friday, May 03, 2002 4:55 PM
To: Kernel Debugging Interest List
Subject: [windbg] Is this expected behavior?

I just got a bugcheck on WinXP while debugging a driver with Windbg
6.0.7. As expected I got the following message:

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, f5c9e7f5}

Probably caused by : fg8100.sys (
fg8100!cfFg8100DeviceControl+68c )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804f784c cc int 3

I then did the !analyze -v but it immediately returns with “The debuggee
is ready to run”. I know what the cause of my bugcheck since the
debugger had a valid stack trace. Is this the expected behavior when a
bugcheck occurs while single stepping (step over) through the code?

  • Steve -

You are currently subscribed to windbg as: xxxxx@thunderstore.com To
unsubscribe send a blank email to %%email.unsub%%

3

Hi Marco,

I was connected to the debugee (using a serial cable) and was actual
stepping over code when the bugcheck occured. I’ve never seen this when
using a crash dump file.

  • Steve -

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven
[mailto:xxxxx@thunderstore.com]
Sent: Friday, May 03, 2002 11:03 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Hi Steve,

I always get the message “The debuggee is ready to run” when doing an
analyze command on a Memory.dmp file. When I connect directly to the
debugee (using a serial 115200 cable connection) this does not happen
and I get all the needed info.

grtx
Marco.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Whitman, Steve
Sent: Friday, May 03, 2002 4:55 PM
To: Kernel Debugging Interest List
Subject: [windbg] Is this expected behavior?

I just got a bugcheck on WinXP while debugging a driver with Windbg
6.0.7. As expected I got the following message:

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, f5c9e7f5}

Probably caused by : fg8100.sys (
fg8100!cfFg8100DeviceControl+68c )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804f784c cc int 3

I then did the !analyze -v but it immediately returns with
“The debuggee
is ready to run”. I know what the cause of my bugcheck since the
debugger had a valid stack trace. Is this the expected
behavior when a
bugcheck occurs while single stepping (step over) through the code?

  • Steve -

You are currently subscribed to windbg as: xxxxx@thunderstore.com To
unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to windbg as: xxxxx@cognex.com
To unsubscribe send a blank email to %%email.unsub%%

4

Did any other debugger commands work? Or do you feel that only !analyze
-v wasn’t working?

Also, did it bugcheck in the same driver you were stepping through or a
different driver?

-----Original Message-----
From: Whitman, Steve [mailto:xxxxx@cognex.com]
Sent: Friday, May 03, 2002 8:46 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Hi Marco,

I was connected to the debugee (using a serial cable) and was actual
stepping over code when the bugcheck occured. I’ve never seen this when
using a crash dump file.

  • Steve -

-----Original Message-----
From: ThunderStore - Marco van Nieuwenhoven
[mailto:xxxxx@thunderstore.com]
Sent: Friday, May 03, 2002 11:03 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Hi Steve,

I always get the message “The debuggee is ready to run” when doing an
analyze command on a Memory.dmp file. When I connect directly to the
debugee (using a serial 115200 cable connection) this does not happen
and I get all the needed info.

grtx
Marco.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Whitman, Steve
Sent: Friday, May 03, 2002 4:55 PM
To: Kernel Debugging Interest List
Subject: [windbg] Is this expected behavior?

I just got a bugcheck on WinXP while debugging a driver with Windbg
6.0.7. As expected I got the following message:

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, f5c9e7f5}

Probably caused by : fg8100.sys (
fg8100!cfFg8100DeviceControl+68c )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804f784c cc int 3

I then did the !analyze -v but it immediately returns with
“The debuggee
is ready to run”. I know what the cause of my bugcheck since the
debugger had a valid stack trace. Is this the expected
behavior when a
bugcheck occurs while single stepping (step over) through the code?

  • Steve -

You are currently subscribed to windbg as: xxxxx@thunderstore.com To
unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to windbg as: xxxxx@cognex.com To
unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

5

The other commands worked. My stack trace indicated the correct
information. It was my driver that bugchecked. I suspect that this was due
to the fact I was stepping over a function when the bugcheck occured.

Since I could use the debugger to find the problem this isn’t a big deal.
But because !analyze didn’t work I didn’t get information about the
bugcheck.

  • Steve -

-----Original Message-----
From: David Holcomb [mailto:xxxxx@microsoft.com]
Sent: Friday, May 03, 2002 12:12 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Did any other debugger commands work? Or do you feel that
only !analyze
-v wasn’t working?

Also, did it bugcheck in the same driver you were stepping
through or a
different driver?

-----Original Message-----
From: Whitman, Steve [mailto:xxxxx@cognex.com]
Sent: Friday, May 03, 2002 8:46 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Hi Marco,

I was connected to the debugee (using a serial cable) and was actual
stepping over code when the bugcheck occured. I’ve never
seen this when
using a crash dump file.

  • Steve -

> -----Original Message-----
> From: ThunderStore - Marco van Nieuwenhoven
> [mailto:xxxxx@thunderstore.com]
> Sent: Friday, May 03, 2002 11:03 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] RE: Is this expected behavior?
>
>
> Hi Steve,
>
> I always get the message “The debuggee is ready to run”
when doing an
> analyze command on a Memory.dmp file. When I connect
directly to the
> debugee (using a serial 115200 cable connection) this does
not happen
> and I get all the needed info.
>
> grtx
> Marco.
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
Whitman, Steve
> Sent: Friday, May 03, 2002 4:55 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Is this expected behavior?
>
>
> I just got a bugcheck on WinXP while debugging a driver with Windbg
> 6.0.7. As expected I got the following message:
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck D1, {0, 2, 1, f5c9e7f5}
>
> Probably caused by : fg8100.sys (
fg8100!cfFg8100DeviceControl+68c )
>
> Followup: MachineOwner
> ---------
>
> nt!RtlpBreakWithStatusInstruction:
> 804f784c cc int 3
>
>
> I then did the !analyze -v but it immediately returns with
> “The debuggee
> is ready to run”. I know what the cause of my bugcheck since the
> debugger had a valid stack trace. Is this the expected
> behavior when a
> bugcheck occurs while single stepping (step over) through the code?
>
> - Steve -
>
>
>
> —
> You are currently subscribed to windbg as:
xxxxx@thunderstore.com To
> unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to windbg as: xxxxx@cognex.com To
> unsubscribe send a blank email to %%email.unsub%%
>

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to windbg as: xxxxx@cognex.com
To unsubscribe send a blank email to %%email.unsub%%

6

Type !analyzebugcheck -v

!analyzebugcheck is a temporary command we added to force analysis no
matter what the state of the target is. This will become !analyze -f in
the next debugger release.

-Andre

7

Should I file a bug on this or is this a known issue?

  • Steve -

-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Friday, May 03, 2002 9:38 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Is this expected behavior?

Type !analyzebugcheck -v

!analyzebugcheck is a temporary command we added to force analysis no
matter what the state of the target is. This will become
!analyze -f in
the next debugger release.

-Andre

You are currently subscribed to windbg as: xxxxx@cognex.com
To unsubscribe send a blank email to %%email.unsub%%