Wireshark-bugs: [Wireshark-bugs] [Bug 9062] Visual C++ Runtime Library Error "The application ha
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 23 Aug 2013 13:31:13 +0000

changed bug 9062

What Removed Added
CC   graham.bloice@trihedral.com

Comment # 5 on bug 9062 from 
Paul,

There are two ways of generating the stack frame:

1.  The user has a Windows debugger (e.g. Visual Studio or WinDbg) and can get
the stack trace from the debugger.  The user must have the pdb's and let their
debugger know where they are.

2.  The user generates a memory dump (basically an image of the faulting
process) and forwards that to someone who has a debugger and the pdb's and they
can see the stack trace and (if a full memory dump is provided) poke around
inside the process image which is frozen as if it had hit a breakpoint.

The memory dump can be generated in a few ways, and there are a few versions of
the dump that only include the stack of the faulting thread, stacks for all
threads or a full memory image.  Obviously the full image can be quite big,
especially if the fault was caused by the process running out of memory but it
does zip up a bit.

To create a full dump file on Windows 7, using Task Manager, switch to the
Processes tab, right click the offending process and select "Create Dump File".
 When the dump is complete, a further dialog will show the path to it.

Zip up the dump file and attach it to the bug.  Note that the dump file will
include some info such as the logged on user name, the computer name and the
domain the computer (if any) belongs to.  In addition, if you have added SSL
master keys to Wireshark, then they may be present in the dump file.

You are receiving this mail because:
  • You are watching all bug changes.