Wireshark mailing list archives
Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010
From: Yang Luo <hsluoyb () gmail com>
Date: Thu, 4 Feb 2016 02:21:53 +0800
OK. I decided to build wpcap.dll with VS2013 at least. And the same issue. (mentioned in the first two posts). It will cause Wireshark on Win8.1/10 x64 to crash. I also used MBCS option instead of Unicode, the same with WinPcap trunk. So weird. I have attached the wpcap.dll file. Substitute it with the original WinPcap/Npcap version in C:\Windows\System32. Then launch Wireshark and you will see the crash. Thanks! On Thu, Feb 4, 2016 at 2:11 AM, Graham Bloice <graham.bloice () trihedral com> wrote:
On 3 February 2016 at 17:44, Gerald Combs <gerald () wireshark org> wrote:It make sense to switch to VS 2015. It uses the Universal CRT, which ships with Windows 10 and is available via Windows Update (KB 2999226) on earlier versions of Windows. I'm hoping to switch Wireshark's Windows installers to VS 2015 before 2.2 is released, but that depends on our third party DLLs (most notably Kerberos).Caution. There have been issues with the Universal CRT, so much so that TortoiseSVN, which jumped onto 2015 very early, now copies the CRT DLL's into the application directory (which is permitted) to avoid the windows update part of the OS portion. As it happens, my next but one task in the day job is to move our build over to VS2015, so I'll be finding out a lot about this in the next 2 weeks. As I think I mentioned last year, I did make changes to our winpcap repo to build under VS2013 (all parts) and I didn't find any deployment issues at all. Hopefully I can check that again very soon. The bit we need to organise is the signing of the build products. I can sign with my companies cert for my testing but obviously can't release that to anyone else. This build of WinPcap was only done to bring the build environment up to date, there were no other functional changes in WinPcap. -- Graham Bloice ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org ?subject=unsubscribe
Attachment:
wpcap.dll
Description:
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Yang Luo (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Pascal Quantin (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Anders Broman (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Yang Luo (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Gerald Combs (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Graham Bloice (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Yang Luo (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Yang Luo (Feb 04)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Anders Broman (Feb 03)
- Re: Wireshark fails to start with wpcap.dll built by Visual Studio 2010 Pascal Quantin (Feb 03)