Warning (Beta): The RVA feature set is in rollout and subject to change and limitations.
XEvent and other outputs (errorlog, sqldump*.txt, …) contain call stack outputs. Some of these outputs are easy to symbolize while others are more difficult.
For example (error log output):
00007FFFF1A66B54 Module(ntdll+00000000000A6B54)
00007FFFEF609F59 Module(KERNELBASE+0000000000139F59)
00007FFF93981D96 Module(sqldk+0000000000011D96)
00007FFF93981CA6 Module(sqldk+0000000000011CA6)
00007FFF93971F9A Module(sqldk+0000000000001F9A)
00007FFF93EA1200 Module(sqlmin+0000000000001200)
00007FFF93EA321E Module(sqlmin+000000000000321E)
00007FFF9397A6C3 Module(sqldk+000000000000A6C3)
00007FFF9397A34D Module(sqldk+000000000000A34D)
00007FFF93979F3E Module(sqldk+0000000000009F3E)
00007FFF93992FA2 Module(sqldk+0000000000022FA2)
00007FFF9399318C Module(sqldk+000000000002318C)
00007FFF93993B83 Module(sqldk+0000000000023B83)
00007FFFEFDD54E0 Module(KERNEL32+00000000000154E0)
00007FFFF19C485B Module(ntdll+000000000000485B)
Using the Windows Debugger you can load the target binary and symbolize using our public symbols.
windbg.exe -z sqldk.dll
> ln sqldk+0000000000023B83
Hint – Use