Re: Open dumps in VS 2005
- From: "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
- Date: Wed, 28 Mar 2007 04:41:06 -0700
Thanks very much for your response. I have tried what you suggest, but when
I open the dmp file (I have to look for it with *.* because in my VS Team
Edition I don´t have any filter for dmp files) VS replies with an error.
The thing is that in the MSDN documentation
(http://msdn2.microsoft.com/en-us/library/fk551230.aspx) it states that dmp
files can only be saved when working with native C++ but it does not state
any restriction when opening the dump files.
What I want to do is to get a dump with the clrdump tool from a WinForms C#
application, and then open the dump to get the exact point in source code
where the app crashes.
So it probably means that VC++ should be installed for dump analysis to work
(I must say I have never installed VS without VC++, and thus cannot know exactly,
of course). Probably the native debug engine gets installed only if the native
dev tools are installed.
An alternative to VS2005 is to use WinDbg for dump analysis. Since you are
going to debug the dump of a managed application, you will have to use command
line SOS anyway, and it does not really matter much what debugger you
are using.
http://msdn.microsoft.com/msdnmag/issues/03/06/Bugslayer/
Yet another note: with .NET 2.0 it is not currently possible (with publicly available
tools) to obtain the source line information from a dump. It is only possible to get
the call stack, and try to guess where in the sources it is.
Oleg
.
- References:
- Re: Open dumps in VS 2005
- From: Oleg Starodumov
- Re: Open dumps in VS 2005
- Prev by Date: Re: Debugging unmanaged dll in .net
- Next by Date: Re: Open dumps in VS 2005
- Previous by thread: Re: Open dumps in VS 2005
- Next by thread: Re: Open dumps in VS 2005
- Index(es):
Relevant Pages
|
Loading