RE: Debugging with dumps
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Thu, 13 Jul 2006 09:17:45 GMT
Hi Mike,
Thanks for your post!
Based on my understanding, you want to display the source line number
regarding certain method in .Net dump file.
I have performed some test regarding this scenario. I directly debug the
..Net application under windbg, so we can first eliminate the dump impact
first.
I found that all the sos.dll extention commands do not include any option
for source code line information.
"SOS Debugging Extension (SOS.dll)"
http://msdn2.microsoft.com/en-us/library/ms404370.aspx
Also, I have tried to use !dumpstack command to get the full managed/native
call stack. Since we are using internal private pdb symbol file, I can see
all the native win32 system dll function source line, however, the output
will eliminate any source line number for .Net method. So I suspect this
information is not avaiable from sos.dll extention command interface.
Anyway, I will try to give it a deeper research and reply to you ASAP.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: Debugging with dumps
- From: Mike Blake-Knox
- Re: Debugging with dumps
- References:
- Debugging with dumps
- From: Mike Blake-Knox
- Debugging with dumps
- Prev by Date: Re: Function names for managed callstack under SOS debugging of .NET 2.0 app
- Next by Date: Re: Debugging with dumps
- Previous by thread: Debugging with dumps
- Next by thread: Re: Debugging with dumps
- Index(es):