custom wireshark build crashing because of Faulting module name: Qt5Widgets.dll
In some of the machines we could install the wireshark exe and able to open the pcap file. But in some of the machines application is crashing because of Qt5Widgets.dll. Please find the attached file for more details. t is capture from Event viewer. General information about the crash is as below:
Faulting application name: Wireshark.exe, version: 2.9.0.0, time stamp: 0x5b96475f
Faulting module name: Qt5Widgets.dll, version: 5.11.1.0, time stamp: 0x5b2360be
Exception code: 0xc0000005
Fault offset: 0x0003aff8
Faulting process id: 0x2af4
Faulting application start time: 0x01d44909a196e7fc
Faulting application path: C:\Program Files (x86)\Wireshark\Wireshark.exe
Faulting module path: C:\Program Files (x86)\Wireshark\Qt5Widgets.dll
Report Id: 3a4187b2-e55b-491e-abae-0c3a3c19c62d
Faulting package full name:
Faulting package-relative application ID:
Note: I could not able to attach png file it says below info: ask.wireshark.org says
60 points required to upload files...
Some questions:
please check inline answers:
OS?
Is this a Wireshark.org produced build or a custom build?
Do you have any custom plugins or scripts or is this "stock" Wireshark?
Does the issue occur when starting Wireshark, or opening an existing capture file, or performing a capture?
Still doubtful it's our build, the build bot is using C:\Qt\5.9.5. I think some one else reported problems with Qt 5.11 but I don't quite remember.
Can you post the contents (Ctrl +C to copy) of the Wireshark Help -> About Wireshark dialog from a machine that is working? I'm looking for the exact version info.
Just i noticed it is custom build one . Please note the information which you asked
(more)You missed off the version info that is just above the Copyright string.
I compiled Wireshark with Qt 5.11.1 and it starts up fine on my computer. Here's my relevant information for comparison:
(more)As do I, and it also works fine for me. For the OP some machines work but others don't. As it's a custom build it would be difficult to debug due to a lack of symbols unless those can be made available.
The build seems to be with msvc 14, perhaps that's a problem.
But so are the others (Chris's and Graham's), so that should be fine.
@grahamb
I've seen that happen before. Should we emphasize the version string in the dialog, to make it more obvious that it's part of the text to copy?
@Jaap, maybe a "Copy" button to automate it all?
For info, my build today using the latest VS 2017 version 15.8.3:
(more)The one build difference that sticks out to me is that both @grahamb and I have Gcrypt 1.8.3 while @aravind has Gcrypt 1.7.6. I'm not sure if this is relevant, but it might be worth updating to see if it makes any difference.
Since it is a custom build , i uninstalled qt511.1 and installed qt 5.9.5 I set the QT5_BASE_DIR environment variable to
(more)E:\Tools\qt\5.9.5\msvc2015_64
. During debug build on microsoft visual studio , build is failing with below error.Delete CMakeCache.txt in the build directory and regenerate the solution by running cmake again.
Thanks mr grahamb.... I tried...no luck... please note i am builing in microsoft visual studio , debug , win32