I am new to windbg.i want to debug a kernel mode device driver which load
at boot time.i have set up two m/c-> Host(P-II,350 MHz,120 MB RAM) and
Target(celeron,300 MHz,32 MB RAM).i have install Windows NT 4.0(checked
build) SP5 on both host and target m/c.i m using Windbg 5.00.2195.1094.
Ever time I set a breakpoint, using the F9 key, in my driver
code, I run and upon hitting the line with the breakpoint,
windbg crashes silently or i want to say it just disappears on my host
machine.Target m/c is stopped at this time. I have to start windbg again
and enable all the options (kernel debugging, symbol path etc)and open the
source code ,all the breakpoints become clear, then run.now command window
showing following lines->
Stopped at unexpected exception: code=80000003 addr=fffffffffc7b1b7c
hard coded break point hit
now target is running.
Can any one suggest me the solution
John
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
Download the 3.00 beta for WinDbg from the WinDbg website.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: xxxxx@yahoo.co.uk [mailto:xxxxx@yahoo.co.uk]
Sent: Monday, July 09, 2001 10:33 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg disappears at breakpoint
I am new to windbg.i want to debug a kernel mode device driver which load
at boot time.i have set up two m/c-> Host(P-II,350 MHz,120 MB RAM) and
Target(celeron,300 MHz,32 MB RAM).i have install Windows NT 4.0(checked
build) SP5 on both host and target m/c.i m using Windbg 5.00.2195.1094.
Ever time I set a breakpoint, using the F9 key, in my driver
code, I run and upon hitting the line with the breakpoint,
windbg crashes silently or i want to say it just disappears on my host
machine.Target m/c is stopped at this time. I have to start windbg again
and enable all the options (kernel debugging, symbol path etc)and open the
source code ,all the breakpoints become clear, then run.now command window
showing following lines->
Stopped at unexpected exception: code=80000003 addr=fffffffffc7b1b7c
hard coded break point hit
now target is running.
Can any one suggest me the solution
John
You are currently subscribed to windbg as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
See my reply to your previous query for context. It has a link to the
download site for the latest WinDBG. You are running one of the most buggy
WinDBG’s in existence.
What is “m/c”?
You don’t need to run the checked build on your debugger host system, and
it’s actually not recommended, just because of the speed issue. Install a
Free build OS on your host, and then install the new WinDBG beta from the
site I sent you last time.
Phil
-----Original Message-----
From: xxxxx@yahoo.co.uk [mailto:xxxxx@yahoo.co.uk]
Sent: Monday, July 09, 2001 10:33 PM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg disappears at breakpoint
I am new to windbg.i want to debug a kernel mode device driver which load
at boot time.i have set up two m/c-> Host(P-II,350 MHz,120 MB RAM) and
Target(celeron,300 MHz,32 MB RAM).i have install Windows NT 4.0(checked
build) SP5 on both host and target m/c.i m using Windbg 5.00.2195.1094.
Ever time I set a breakpoint, using the F9 key, in my driver
code, I run and upon hitting the line with the breakpoint,
windbg crashes silently or i want to say it just disappears on my host
machine.Target m/c is stopped at this time. I have to start windbg again
and enable all the options (kernel debugging, symbol path etc)and open the
source code ,all the breakpoints become clear, then run.now command window
showing following lines->
Stopped at unexpected exception: code=80000003 addr=fffffffffc7b1b7c
hard coded break point hit
now target is running.
Can any one suggest me the solution
John
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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