I thought this might be addressed in the new 2.0 release, but it appears
not. Perhaps it is my mental model that needs addressing? 
If I set a BP using bu driver!routine, then save my workspace, then reboot
the system, I don’t hit the breakpoint unless I set WinDBG to request the
initial breakpoint. If I just let it start without the initial BP, and there
are not hard-coded BPs, no breakpoints are ever instantiated until I break
in somehow, such as sending a break signal. If there is a hard-coded BP
anywhere, all BPs are enabled after hitting the hardcoded BP.
In other words, BPs that are saved in the workspace don’t seem to be
instantiated unless there is a BP that isn’t part of the workspace first.
Is this by design? The docs don’t mention this, at least not on the page
where most of the other info about BPs is found. So is my usage model
broken, or is it unreasonable to expect that I should get the BPs I’ve set
and saved? I work around it by always setting the initial BP, and maybe
that’s the way it’s supposed to be, but it was sure confusing for a while
until I discovered that.
Thanks,
Phil
* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com