windbg disassembly error

Ivan Brugiolo [MSFT]

2003-08-06 02:29:30 UTC

IA64 is particularly prone to this 'overload' because it uses function
and function descriptors that may have the same name,
depending on how and which symbols are loaded

in this case I explicitely fooled the symbol resolution, and I got the
Function descriptor.

0: kd> x nt!KeBugCheck
e0000000`830077b0 nt!KeBugCheck = <no type information>
0: kd> dq e0000000`830077b0 l2
e0000000`830077b0 e0000000`83069820 e0000000`8346a000
0: kd> u e0000000`83069820
nt!LsaDeregisterLogonProcess+0x5ce60:
e0000000`83069820 alloc r34=ar.pfs, 3, 0, 6, 0 <<<<<<<<<<<<<<< good
prologue
e0000000`83069824 mov r33=rp
e0000000`83069828 addl r36=0, r0
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Pat [MSFT]
That usually means that there is more than one function of that name (i.e.
the function is overloaded). So, when you give just the function, name
WinDbg/KD doesn't know which version to print. When you use the address, it
does. You can see the various functions by doing 'x nt!KeBugCheckEx
<enter>'
Pat

I am looking at an IA-64 dump. As I use u to disassemble
0: kd> u nt!kebugcheckex
I get this error and no assembly code displayed.
Matched: e0000000`83079180 nt!KeBugCheckEx = <no type
information>
Ambiguous symbol error at 'nt!kebugcheckex'
However, when I type this I see the assembly code fine.
0: kd> u e000000083079180
What does this error mean? FYI: I'm running Windbg
6.2.0013.0.
Thanks in advance,
Usha