One of the students in debug class this week asked a question to which I
didn’t have an answer so I figured I’d ask.
On x86, a stack backtrace (e.g, “kv”') labels the calls as the “Call
Stack”
On amd64, a stack backtrace labels the calls as the “Call Site”
What is the significance of the different nomenclature used in each of
these cases (my “guess” was just that someone typed it in differently in
the print statement, but perhaps there is some deeper meaning lurking
below the surface?)
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
Which labels are you referring to? The immediate column headers in kv
output? I don’t think there’s a label on x86. If there is a call-stack
vs. call-site difference it doesn’t really mean anything.
For x86 the output should be:
kd> kv
ChildEBP RetAddr Args to Child
f6bc6b48 804d7c50 0000000a 00001000 00000002 nt!KeBugCheckEx+0x19 (FPO:
[Non-Fpo]) (CONV: stdcall)
For non-x86 it should be:
1: kd> kv
Child-SP Child-BSP RetAddr Call Site
e0000165dd9164f0 e0000165dd918480 e0000000`83067df0
nt!KeBugCheck2+0x110
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Thursday, February 09, 2006 8:23 AM
To: Kernel Debugging Interest List
Subject: [windbg] Stack trace info question
One of the students in debug class this week asked a question to which I
didn’t have an answer so I figured I’d ask.
On x86, a stack backtrace (e.g, “kv”') labels the calls as the “Call
Stack”
On amd64, a stack backtrace labels the calls as the “Call Site”
What is the significance of the different nomenclature used in each of
these cases (my “guess” was just that someone typed it in differently in
the print statement, but perhaps there is some deeper meaning lurking
below the surface?)
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com