c# - Analyzing a CLR .dmp file in WinDbg -


i have c# .net 3.5 application created in visual studio 2008 crashing on windows xp sp3 (x86) pc no development environment.

i have been able .dmp file pc , take windows 7 64-bit development pc , load windbg 6.12.

but, can't see code in call stack c# application. looks it's entirely native call stack.

the result !analyze -v below.

i have relevant exe, dll, , pdb files in same directory .dmp. executable crashed compiled in debug mode.

i have visual studio 2008, if that's easier use. opening dump file in there shows native call stack, nothing code.

how can view clr call stack?

0:004> !analyze -v ******************************************************************************* *                                                                             * *                        exception analysis                                   * *                                                                             * *******************************************************************************   faulting_ip: kernel32!raiseexception+53 7c812afb 5e              pop     esi  exception_record:  0392f018 -- (.exr 0x392f018) exceptionaddress: 7c812afb (kernel32!raiseexception+0x00000053)    exceptioncode: e0434f4d (clr exception)   exceptionflags: 00000001 numberparameters: 1    parameter[0]: 80070057  process_name:  foo.exe  error_code: (ntstatus) 0xe0434f4d - <unable error code text>  exception_code: (ntstatus) 0xe0434f4d - <unable error code text>  exception_parameter1:  80070057  mod_list: <analysis/>  managed_stack: !dumpstack -ee no export dumpstack found  managed_bitness_mismatch: managed code needs matching platform of sos.dll proper analysis. use 'x86' debugger.  additional_debug_text:  followup set based on attribute [is_chosencrashfollowupthread] frame:[0] on thread:[pseudo_thread]  last_control_transfer:  79ef2bfc 7c812afb  faulting_thread:  ffffffff  default_bucket_id:  stackimmune  primary_problem_class:  stackimmune  bugcheck_str:  application_fault_stackimmune_nosos_clr_exception  stack_text: 00000000 00000000 foo.exe+0x0   symbol_name:  foo.exe  followup_name:  machineowner  module_name: foo  image_name:  foo.exe  debug_flr_image_timestamp:  4d5da0cd  stack_command:  ** pseudo context ** ; kb  failure_bucket_id:  stackimmune_e0434f4d_foo.exe!unknown  bucket_id:  application_fault_stackimmune_nosos_clr_exception_foo.exe  followup: machineowner --------- 

managed code needs matching platform of sos.dll proper analysis. use 'x86' debugger.

you have use x86 debugger/windbg debug x86 memory dump. use .loadby sos mscorwks load appropriate sos. verify if extension loaded using .chain command.

tess has debugging tutorials.


Comments

Popular posts from this blog

c# - How to set Z index when using WPF DrawingContext? -

razor - Is this a bug in WebMatrix PageData? -

visual c++ - Using relative values in array sorting ( asm ) -