• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 330
  • Last Modified:

Current line

Hi all,
 I just wonder what command help me to know the current line at which i am running debugger in windbg? Thanks.
0
valleytech
Asked:
valleytech
  • 3
  • 2
  • 2
1 Solution
 
valleytechAuthor Commented:
kd> l-t
Source options are e:
     2/l - List source line at prompt
     4/s - List source code at prompt
     8/o - Only show source code at prompt

====> when i type l-t, i got that notes. I dont' understand their meaning. Please help.
0
 
alainbrydenCommented:
just type backtrace, and it should tell you where you are in each nested method
0
 
valleytechAuthor Commented:
when i type "backtrace", i got syntax error.
0
Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

 
dimitryCommented:
Try:
kd> u
(Unassemble next few instructions)
0
 
alainbrydenCommented:
I'm sorry you're using windbg I was thinking of unix dbg
0
 
valleytechAuthor Commented:
kd>u doesn't work

kd> u
nt!KeUpdateSystemTime+0x142:
805120f8 ebb4             jmp     nt!KeUpdateSystemTime+0xf8 (805120ae)
nt!KeUpdateRunTime:
805120fa a11cf0dfff       mov     eax,[ffdff01c]
805120ff 53               push    ebx
80512100 ff80c4050000     inc     dword ptr [eax+0x5c4]
80512106 8b9824010000     mov     ebx,[eax+0x124]
8051210c 8b4b44           mov     ecx,[ebx+0x44]
8051210f f7457000000200   test    dword ptr [ebp+0x70],0x20000
80512116 753e             jnz     nt!KeUpdateRunTime+0x60 (80512156)
kd> bl
 0 eu             0001 (0001) (@@masm(`hello.c:22+`))
 1 eu             0001 (0001) (@@masm(`hello.c:22+`))
 2 eu             0001 (0001) (DriverEntry)
 3 eu             0001 (0001) (DriverEntry)
 4 eu             0001 (0001) (DriverEntry)
 5 e 805120ac     0001 (0001) nt!KeUpdateSystemTime+0xf6

kd> l+t
Source options are f:
     1/t - Step/trace by source line
     2/l - List source line at prompt
     4/s - List source code at prompt
     8/o - Only show source code at prompt
kd>
Source options are f:
     1/t - Step/trace by source line
     2/l - List source line at prompt
     4/s - List source code at prompt
     8/o - Only show source code at prompt
0
 
dimitryCommented:
Host: Adi (Microsoft)
Q: How to debug source code in NTSD/KD (in a similar way as in WinDbg)?

A: The commands are ".lines" followed by "l+*". Following that, you can step directly into source code, and "ls." will show you the current source. Before that, you need to run ".srcpath" to set the path to the source.

Host: Ilyak (Microsoft)
Q: How to debug source code in NTSD/KD (in a similar way as in WinDbg

A: l+l;l+s;l+t first: Then can do lsa, ls, lsp, lsc, lsf -- read doc

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now