Re: WER and managed minidumps

Thanks, that helps alot, getting much further

now, is there a way i can reference actual line numbers?

0:000> !clrstack
OS Thread Id: 0x854 (0)
ESP EIP
0012f01c 7c82ed54 [HelperMethodFrame: 0012f01c]
0012f0c0 79601f82 System.String.InternalSubStringWithChecks(Int32, Int32,
Boolean)
0012f0d4 0378e8cb ShoutMonitor.ValueList..ctor(System.String)
0012f0f0 03910f59 ShoutMonitor.ShoutState.ProcessChannel(System.String,
Boolean)
0012f138 0378d0f4 ShoutMonitor.ShoutState.Process(Int32, System.String)
....
don't actually see line number, (even with !clrstack -a)
!anaylze -v does show manged stack with address offsets however still no
line numbers?

MANAGED_STACK:
(TransitionMU)
0012F0C0 79601F82
mscorlib_ni!System.String.InternalSubStringWithChecks(Int32, Int32,
Boolean)+0x2b7082
0012F0D4 0378E8CB VXmonitor!ShoutMonitor.ValueList..ctor(System.String)+0xbb
0012F0F0 03910F59
VXmonitor!ShoutMonitor.ShoutState.ProcessChannel(System.String,
Boolean)+0x21
0012F138 0378D0F4 VXmonitor!ShoutMonitor.ShoutState.Process(Int32,
System.String)+0xdc
0012F15C 0378CFD0
VXmonitor!ShoutMonitor.ShoutState.ProcessChunk(System.String)+0x150
....

Cheers
Tony


"Oleg Starodumov" <com-dot-debuginfo-at-oleg> wrote in message
news:OsWkroN%23GHA.2180@xxxxxxxxxxxxxxxxxxxxxxx
I have been trying to get the minidumps from windows error reporting to
open
correctly in visual studio 2005.
it's a managed c# application. and the WER site shows the crash a
"managed
crash" however when i try and open the mdmp file and load it and point my
pdb at it (as well as the symbol server for everything else)

Problem is it seems to debug the dump as native, so when it loads the
symbols for my app in the pdb it says "no native symbols in symbol file"
(resulting in only a partial stack trace) which i presume means the the
debugger is only looking for native symbols (not managed).


VS2005 debugger always works in native mode when debugging dumps.
For managed debugging, you should use SOS extension in Immediate
window (or use WinDbg, which can also use SOS).

You load SOS like this:

.load <.net_2.0_install_dir>\sos.dll

And then e.g. print managed call stack using

!clrstack

More information about SOS you can find here:
http://mtaulty.com/communityserver/blogs/mike_taultys_blog/archive/2004/08/03/4671.aspx
http://msdn.microsoft.com/msdnmag/issues/03/06/Bugslayer/default.aspx
http://blogs.msdn.com/tess
(though note that the information contained in a dump created with WER
will probably only be enough to get the managed call stack and nothing
more,
due to small size of the dump)

other issues are: "no matching binary found" stuff like:
C:\WINDOWS\assembly\NativeImages_v2.0.50727_32System.Drawing\c152a840d3c3054fbdcbc6a0e8f65bde\System.Drawing.ni.dll

C:\WINDOWS\assembly\NativeImages_v2.0.50727_32System.Windows.Forms\70e41dc5673fcd42be7b347bdcdef6ec\System.Windows.Forms
.ni.dll

etc.

how can i resolve this?


These are NGEN-ed modules, which are generated anew on each system,
so usually it is not possible to find matching binaries unless you copy
them
from the system where the dump was created.

But in most cases these modules are not needed for effective debugging
with SOS
(at least in .NET 2.0), and the debugger should be able to read the
necessary
metadata from the original modules (which should be on the module search
path).

--
Oleg
[VC++ MVP http://www.debuginfo.com/]







.

Relevant Pages

  • Re: WER and managed minidumps
    ... debugger is only looking for native symbols. ... VS2005 debugger always works in native mode when debugging dumps. ... you should use SOS extension in Immediate ... (though note that the information contained in a dump created with WER ...
    (microsoft.public.vsnet.debugging)
  • Re: Crashdump Win2k Server
    ... I'm afraid that mini dump is too limited to analyze and obtain enough ... I suggest that you config "Write debugging information" to Complete memory ...
    (microsoft.public.windows.server.general)
  • Re: Exception and GetLastError()
    ... blah blah blah ... e.g. as a mini dump. ... Those dump files can be loaded with windbg from the debugging sdk so that you can analyze the state of a process when an exception occurs. ...
    (microsoft.public.vc.language)
  • Re: Memory.dmp
    ... >>The computer has rebooted from a bugcheck. ... >>How can i found out what causes the reboot? ... This means the dump contains ... > code and has to be analyzed using a debugging program. ...
    (microsoft.public.win2000.general)
  • [PATCH 09/44 take 2] [UBI] debug unit header
    ... * the GNU General Public License for more details. ... * UBI debugging unit. ... The debugging prints may also be directed to the console. ... * @vtr: the object to dump ...
    (Linux-Kernel)