Why don’t you just put a hard coded break point in your driver entry,
then when the machine boots up again, you will be able to set the
correct location of the break point that you want? Something like the
following:
/***********************************************************************
***
if the debugger is hooked up, lets break into it so we can load
our
symbols and set any break points we want. This will only happen
in
debug mode
************************************************************************
*/
TRAP();
Where TRAP is defined as follows:
#if DBG
#define TRAP() DbgBreakPoint()
#else // !DBG
#define TRAP()
#endif
–
Michael Smith, SMTS
Senior Software Engineer
Ethernet Division
agere systems
1110 American Parkway NE
Lehigh Valley Central Campus
Room 10H-310B
Allentown, PA 18109 USA
Phone: (610) 712-6353
Fax : (610) 712-1178
Email: xxxxx@agere.com
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brian Stark
Sent: Monday, May 08, 2006 11:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] reconnecting after hibernate
I am trying to debug an issue with my power dispatch routine using
windbg and 1394. When I set the target to hibernate I lose connection,
which is understandable, but the connection is not re-established and I
miss the breakpoint I am looking for when powering back up. My thought
is to put an assertion where I want the break to happen, is there a
better way?
Brian D. Stark
Lead Software Engineer
Connectivity Products Group
Mobility Electronics, Inc. (NASDAQ: MOBE)
9918 Via Pasar
San Diego, CA 92126
www.mobilityelectronics.com http:</http:>
w: 858.530.2511 x245
m: 760.889.2774
fax: 480.281.7833
xxxxx@mobl.com
CONFIDENTIALITY NOTICE: The information in this electronic mail
transmission is legally privileged and confidential information intended
only for the use of the individual or entity named above. If the reader
of this message is not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of the transmission is
strictly prohibited. If you have received this transmission in error,
delete the message and immediately notify us by telephone at
480.596.0061 or by responding to this email.
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com