Windbg exits when trying to attach to a target sitting at a break (1394)

WINDBG
1

WindBg from the WDK 7600.16385.1 (6.12.0002.633) AMD64. connected via
1394

I start a target without letting windbg continue from a dialogue and then
run it to a hard coded DbgBreakPoint().
I then start windbg and try to attach.
It silently exits. I have tried attaching another windbg to it but it
doesn’t see much except:

Debug target initialization failed, 0x8000FFFF

This is slightly more annoying than the previous versions habit of just
crashing when the target rebooted.

This release also seems to be much worse at the “sit doing nothing but
chewing CPU even with no network in the symbol path” thing than the previous
versions, but I have not had a chance to capture some stacks. I’ll do so
and get back to you…

Also, how can I install the x86 version ? This isn’t really important since
I learnt many year ago to preciously hoard all my previous windbg installs
so that I can use the correct one for each problem, but it would be nice to
know…

2

Hmm. I always start Windbg before the target, and use the first symbol load
bp, as that has proven very reliable over the various versions.

I haven’t noticed a CPU usage issue yet.

I didn’t like the WDK installer’s default location, so I told the WDK
installer not to install the debugger, then I ran both the x86 and x64
windbg .msi files directly from the mounted ISO.

Phil

Philip D. Barila??? (303) 776-1264

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rod Widdowson
Sent: Wednesday, December 01, 2010 9:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg exits when trying to attach to a target sitting at
a break (1394)

WindBg from the WDK 7600.16385.1 (6.12.0002.633) AMD64. connected via
1394

I start a target without letting windbg continue from a dialogue and then
run it to a hard coded DbgBreakPoint().
I then start windbg and try to attach.
It silently exits. I have tried attaching another windbg to it but it
doesn’t see much except:

Debug target initialization failed, 0x8000FFFF

This is slightly more annoying than the previous versions habit of just
crashing when the target rebooted.

This release also seems to be much worse at the “sit doing nothing but
chewing CPU even with no network in the symbol path” thing than the previous

versions, but I have not had a chance to capture some stacks. I’ll do so
and get back to you…

Also, how can I install the x86 version ? This isn’t really important since
I learnt many year ago to preciously hoard all my previous windbg installs
so that I can use the correct one for each problem, but it would be nice to
know…

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

3

Why don’t you fire up the debugger before you boot the target?

Let the debugger connect during boot, and everything should be fine when you hit your hard coded breakpoint.

The other thing to do, is make sure that you actually have the latest version of the 1394 debug driver in your host system32\drivers directory.

If not, then copy the newer one from debuggerinstalllocation\1394\1394kdbg.sys into your system32\drivers directory and overwrite the old one.

Reboot your host.

It sounds like you may have installed an old version of the debugger on your system recently, and so the forced upgrade of the 1394 debug driver is not working as intended when you fire up 1394 debugging using the latest release.

Also make sure that you don’t have the completely ancient version of the 1394 debug driver sitting around on your box. I don’t recall the name of the really old driver, but you should only have 1394kdbg.sys - nothing else. There were extensive release notes that shipped with the debugger a few releases back that explained how to purge your system of the no longer supported debug driver.

The debugger and the debug driver are rather tightly coupled, and so trying to use a new debugger with the old driver is not going to work well.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Rod Widdowson
Sent: Wednesday, December 01, 2010 8:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg exits when trying to attach to a target sitting at a break (1394)

WindBg from the WDK 7600.16385.1 (6.12.0002.633) AMD64. connected via
1394

I start a target without letting windbg continue from a dialogue and then
run it to a hard coded DbgBreakPoint().
I then start windbg and try to attach.
It silently exits. I have tried attaching another windbg to it but it
doesn’t see much except:

Debug target initialization failed, 0x8000FFFF

This is slightly more annoying than the previous versions habit of just
crashing when the target rebooted.

This release also seems to be much worse at the “sit doing nothing but
chewing CPU even with no network in the symbol path” thing than the previous
versions, but I have not had a chance to capture some stacks. I’ll do so
and get back to you…

Also, how can I install the x86 version ? This isn’t really important since
I learnt many year ago to preciously hoard all my previous windbg installs
so that I can use the correct one for each problem, but it would be nice to
know…

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

>“Joe Ballantyne” wrote in message news:xxxxx@windbg…

Why don’t you fire up the debugger before you boot the target?

I do. Always. The issue comes if I have edited a source file and windbg
wants to reload it when it detaches. It throws a popup which stalls Wingbg.
I get through the boot sequence start my test, hit the breakpoint and give
focus to windbg and there is is mocking me at a modal dialogue :-).

As an aside I have always required the modal dialogue box because the fact
that Wingbg cannot attach to a rebooting VMware box (historically). Of
course I use KDVM these days so I don’t need that and that may fix my
problem.

The other thing to do, is make sure that you actually have the latest
version of the 1394 debug driver in your host system32\drivers directory.

It would be difficult to see how since this is a pristine install on ground
up Win7 rebuild. I’ve checked the SHAs on both files and they are the same.

I did however rename away 1394bus.sys (which will probably kill my ability
to do anything but debug on that port, but this is not an issue for me) and
that did help. It might of course just be a Heisenbug which has moved, but
for now I am doubly fixed).

Thanks for the pointers.

“Philip D Barila” wrote in message news:xxxxx@windbg…
I didn’t like the WDK installer’s default location, so I told the WDK
installer not to install the debugger, then I ran both the x86 and x64
windbg .msi files directly from the mounted ISO.

neat trick. Thanks.

5

If that doesn’t work, there’s a long series of steps in the relnotes.txt
file about how to get the correct version of the 1394 drivers to install.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Wednesday, December 01, 2010 3:09 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Windbg exits when trying to attach to a target sitting
at a break (1394)

Why don’t you fire up the debugger before you boot the target?

Let the debugger connect during boot, and everything should be fine when you
hit your hard coded breakpoint.

The other thing to do, is make sure that you actually have the latest
version of the 1394 debug driver in your host system32\drivers directory.

If not, then copy the newer one from
debuggerinstalllocation\1394\1394kdbg.sys into your system32\drivers
directory and overwrite the old one.

Reboot your host.

It sounds like you may have installed an old version of the debugger on your
system recently, and so the forced upgrade of the 1394 debug driver is not
working as intended when you fire up 1394 debugging using the latest
release.

Also make sure that you don’t have the completely ancient version of the
1394 debug driver sitting around on your box. I don’t recall the name of
the really old driver, but you should only have 1394kdbg.sys - nothing else.
There were extensive release notes that shipped with the debugger a few
releases back that explained how to purge your system of the no longer
supported debug driver.

The debugger and the debug driver are rather tightly coupled, and so trying
to use a new debugger with the old driver is not going to work well.

Joe.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rod Widdowson
Sent: Wednesday, December 01, 2010 8:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg exits when trying to attach to a target sitting at
a break (1394)

WindBg from the WDK 7600.16385.1 (6.12.0002.633) AMD64. connected via
1394

I start a target without letting windbg continue from a dialogue and then
run it to a hard coded DbgBreakPoint().
I then start windbg and try to attach.
It silently exits. I have tried attaching another windbg to it but it
doesn’t see much except:

Debug target initialization failed, 0x8000FFFF

This is slightly more annoying than the previous versions habit of just
crashing when the target rebooted.

This release also seems to be much worse at the “sit doing nothing but
chewing CPU even with no network in the symbol path” thing than the previous

versions, but I have not had a chance to capture some stacks. I’ll do so
and get back to you…

Also, how can I install the x86 version ? This isn’t really important since
I learnt many year ago to preciously hoard all my previous windbg installs
so that I can use the correct one for each problem, but it would be nice to
know…

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