1 | initial version |
Unless you have modified the defaults, the crash dump will be in %LOCALAPPDATA%\CrashDumps
You can load the dump file in Visual Studio, or WinDbg. WinDbg has the !analyze command to triage the crash.
To make much sense of the crash you will need the debug symbols, these can be obtained from the download server, look for wireshark-pdb-winxx-3.2.5.zip
where winxx is win32 or win64 for the bitness of Wireshark you have installed. Note that due to "issues", some pdb files were not uploaded by the build process so aren't available. Unfortunately 3.2.5 was one of the affected versions. You'll need to tell the debugger where to find the symbols once you extract them from the zip.
To look any further into the crash you will also need the sources, a tarball or git checkout of the tag will be sufficient.
Finally, 3.2.x is close to end of life. If you can create the crash with the current stable version, please submit that first and it will be backported as appropriate.