I am coming back after many many years back to using WinDbg. Boot,ini days are gone and I have set up using bcdedit. However I want to break in right after system boot that is before any other driver gets loaded. In the boot.ini if I recall right we used to set break=1 and debugger would break. I checked the usage of bcdedit and it does not have any such option of setting the break point. So how do I do that? Please advise.
Use msconfig to enable debugger. The initial breakpoint is enabled when (or after) you start the debugger, by a command line option or a command.
Ah! Got it, msconfig is same as editing boot.ini and you do it in the target system. On the host you run WinDbg -d and that will ensure breaking at the very first opportunity. They said -b option is not supported anymore. This should work for me. Later on I will figure out and try the command also. Thanks Alex
Debug –> Kernel Connection –> Cycle Initial break or Ctrl-Alt-K will also have the same affect as WinDng -d. Just wanted to complete the answers to my questions.
assuming you have a running kd connection and you wish to start over again
issuing sxe ibp ; .reboot
will request an initial breaking during the next boot (.reboot forces
reboot of target immediately )
i havent checked this in 8 and > so not sure if there is any change in
the behaviour
but downline it used to work fine infact in xp there was no need to
even do /break edit in boot.ini
On 1/28/14, xxxxx@gmail.com wrote:
> Debug –> Kernel Connection –> Cycle Initial break or Ctrl-Alt-K will also
> have the same affect as WinDng -d. Just wanted to complete the answers to my
> questions.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>