You have the (unmanaged) offset within the Method. Unfortunately there is not direct way to retrieve e.g. the Source-Code line of the corresponding IL-Statement. You have to use something like !U (“annotated” disassembly for managed code) and figure it out by yourself.
For a pure native application you just have to query the debugging symbols (ln ADDRESS)
GP
-----Urspr?ngliche Nachricht-----
Von: Lin George [mailto:xxxxx@yahoo.com]
Gesendet: Dienstag, 03. M?rz 2009 10:22
An: G?nter Prossliner
Cc: xxxxx@lists.osr.com
Betreff: Re: AW: [windbg] help to send me “Windbg stack trace issue” discussion email?
Thanks GP!
I further question, are there any ways to know the related managed source code for a crash address? Currently from your solution, I know which method causes crash, but since the method is long, will be great if I could fast find which line of source code causes such issue.
If my application is pure native application, how do you find related source code for a crash address?
regards,
George
powered by Exchange 2007 - hosted by a Microsoft Gold Partner - visit us www.world-direct.at
I have tried to use !u and even if !uf, the annotated information is very less – just include the place when I do method call and when I create a new instance of some type of objects, do you have any experience sharing about how to use !u to find related source codes?
For 2,
Could you show me which command(s) do you use in pure native code to “query the debugging symbols” (I think you mean query line number?) for a specific IP address?
regards,
George
----- Original Message ----
From: G?nter Prossliner To: Kernel Debugging Interest List Cc: “xxxxx@lists.osr.com” Sent: Tuesday, March 3, 2009 5:26:04 PM Subject: AW: AW: [windbg] help to send me “Windbg stack trace issue” discussion email?
Hello George,
1. You have the (unmanaged) offset within the Method. Unfortunately there is not direct way to retrieve e.g. the Source-Code line of the corresponding IL-Statement. You have to use something like !U (“annotated” disassembly for managed code) and figure it out by yourself.
2. For a pure native application you just have to query the debugging symbols (ln ADDRESS)
GP
-----Urspr?ngliche Nachricht----- Von: Lin George [mailto:xxxxx@yahoo.com] Gesendet: Dienstag, 03. M?rz 2009 10:22 An: G?nter Prossliner Cc: xxxxx@lists.osr.com Betreff: Re: AW: [windbg] help to send me “Windbg stack trace issue” discussion email?
Thanks GP!
1.
I further question, are there any ways to know the related managed source code for a crash address? Currently from your solution, I know which method causes crash, but since the method is long, will be great if I could fast find which line of source code causes such issue.
2.
If my application is pure native application, how do you find related source code for a crash address?
regards, George
powered by Exchange 2007 - hosted by a Microsoft Gold Partner - visit us www.world-direct.at
