Thank you for your response.
I always keep the “source mode on” button on. I also try to use t+t, t+* and
.lines -e.
The symbol was also loaded correctly.
Here is the output of windbg command window:
Breakpoint 0 hit
1264: {
kd> L+*
Source options are ffffffff:
1/t - Step/trace by source line
2/l - List source line for LN and prompt
4/s - List source code at prompt
8/o - Only show source code at prompt
kd> .lines -e
Line number information will be loaded
kd> lm
start end module name
80001000 8000ae00 pcmcia (deferred)
8000b000 80011b20 atapi (deferred)
80012000 8001a960 scsiport (deferred)
8001b000 8001ea80 disk (deferred)
8020a000 80210660 atdisk (deferred)
80211000 802144a0 class2 (deferred)
80215000 80237a40 fastfat (deferred)
80238000 802397c0 intlfxsr (deferred)
804d0000 805b3700 nt (codeview symbols)
f:\symbols\nt4sp6a\symbols\exe\ntoskrnl.dbg
805b4000 805c0c80 hal (deferred)
a0000000 a013f920 win32k (codeview symbols)
f:\symbols\nt4sp6a\symbols\sys\win32k.dbg
f2c00000 f2c0a820 8620 (deferred)
f2c10000 f2c187c0 dtv (deferred)
f2c30000 f2c39520 npfs (deferred)
f2eb8000 f2ebd6a0 msfs (deferred)
f2f08000 f2f0d5a0 cdrom (deferred)
f2f58000 f2f5f2e0 i8042prt (deferred)
f2f70000 f2f76100 videoprt (deferred)
f2fe0000 f2fe7100 netbios (deferred)
f3078000 f307a4a0 ksecdd (deferred)
f3080000 f3082400 mouclass (deferred)
f3088000 f308a3a0 kbdclass (deferred)
f3098000 f309a4e0 tdi (deferred)
f30a0000 f30a3860 vga (deferred)
f310c000 f310d820 fs_rec (deferred)
f3116000 f3117d20 biosdl32 (deferred)
f31cb000 f31cb9e0 null (deferred)
f31cc000 f31ccf00 beep (deferred)
f8ecb000 f8f051a0 srv (deferred)
f8f06000 f8f19960 mup (deferred)
f8f1a000 f8f5aa20 rdr (deferred)
f8f83000 f8f93220 afd (deferred)
f8f94000 f8fb2940 netbt (deferred)
f8fb3000 f8fd8c00 tcpip (deferred)
f8fd9000 f8ff1600 nbf (deferred)
f9862000 f98914e0 sgiul40 (codeview symbols)
g:\nt40ddk\lib\i386\checked\SGIUL40.dll
f98ba000 f98d7f60 ndis (deferred)
fa938000 fa94cac0 sgiulnt (deferred)
Unable to examine unloaded module list
kd> p
sgiul40!DrvCopyBits+1:
f9863fe2 8bec mov ebp,esp
kd> p
sgiul40!DrvCopyBits+3:
f9863fe4 83ec10 sub esp,0x10
kd> p
1281: DISPDBG((2, “CopyBit - enter”));
Thanks
ZhigangXu
-----Original Message-----
From: Barila, Phil [SMTP:xxxxx@intel.com]
Sent: Thursday, July 19, 2001 3:48 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Step over incorrect
Make sure you have Debug->Source Mode selected. Make sure your build
environment is producing symbolic debugging information.
Phil
* Philip D. Barila | (503) 264-8386
* Intel Corp. | Not speaking for Intel
-----Original Message-----
From: Zhigang Xu [mailto:xxxxx@trident.com.cn]
Sent: Wednesday, July 18, 2001 10:53 PM
To: Kernel Debugging Interest List
Subject: [windbg] Step over incorrect
Hi all,
I used windbg(Version 3.0.0010.0) to debug a driver in WinNT 40. But I can
not get step over (F10) correctly as I did in Win2K. F10 just steps over
an instruction of x86 in source code mode. I used NT40 DDK and VC6 to
build this driver. It is not convenient to use several F10s to go through
a C instruction.
How can I get it correctly?
Thanks
ZhigangXu
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: xxxxx@trident.com.cn
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