CODEWITHSUNDEEP
debuggingkernelwindbgremote-debugging
anishsane
anishsane

Reputation: 20980

detatch windbg kernel debugger & keep target running

Consider below scenario:

  1. I have setup debug over serial port on a windows 7 system.
  2. On another machine, I have installed windbg & connected serial cable between them.

When I start the target machine, & have windbg running on debugger machine, the connection between windbg & windows kernel gets established properly & I am able to debug as per what I want.

My problem is:

When the connection is established, there is no way to detatch the kernel debugging & allow it to run as stand-alone.
I often need to remove / re-install driver. Having the debugger attached is completely un-necessarily for this & it makes the installation very slow.

Simple solution is not starting windbg at all. But is there a way to just detatch debugger & allow the system to free-run, after the connection was established? Currently, detatching the debugger keeps the target system in frozen state, allowing the user to be re-connected again.

NOTE: Any hacky way is welcome too. There is no clean way. (known to me at least.)

Upvotes: 2

Views: 945

Answers (2)

Rahul Sundar
Rahul Sundar

Reputation: 490

Usually on reboot it would be slow because it retrieves and loads all the symbols. Caching the symbols on host machine would improve the speed to some extent. And an another tip whenever you felt it got stuck or slower..is to press Ctrl + Brk to abort any long stuck loading operation and press F5 to continue run.

Upvotes: 0

snoone
snoone

Reputation: 5499

Not that I'm aware of. I remember at some point (XP, maybe?) the target machine would time out after a while (30-60 seconds) and continue running, but I don't think that's true any longer.

Can you use .kdfiles instead of uninstalling/re-installing? Or, even better, switch to 1394.

Upvotes: 1

Related Questions