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).
On 2/3/16 8:59 AM, Yang Luo wrote:
> Hi Anders,
>
> Building with VS 2013 means the Npcap user has to get a VC 2013 redist
> installed, which is not always the case (at least fewer installed than VC
> 2010 redist package). Actually, once a user complains that Npcap fails to
> run and I found it's because of the unavailability of correct VC redist.
> And, Npcap is only 600+KB and a VC redist package can be 7+MB. So it's not
> good for Npcap installer to ship with a VC redist like what Wireshark
> currently did. Do you have any better solutions?
>
> Cheers,
> Yang
>
>
> On Thu, Feb 4, 2016 at 12:46 AM, Anders Broman <anders.broman@xxxxxxxxxxxx
> <mailto:anders.broman@xxxxxxxxxxxx>> wrote:
>
> Hi,____
>
> Why not build with VS 2013? It seems to be supported in master now. I
> presume we would like updates pushed there.____
>
> Regards____
>
> Anders____
>
> __ __
>
> *From:*wireshark-dev-bounces@xxxxxxxxxxxxx
> <mailto:wireshark-dev-bounces@xxxxxxxxxxxxx>
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx
> <mailto:wireshark-dev-bounces@xxxxxxxxxxxxx>] *On Behalf Of *Pascal Quantin
> *Sent:* den 3 februari 2016 17:27
> *To:* Developer support list for Wireshark
> *Subject:* Re: [Wireshark-dev] Wireshark fails to start with wpcap.dll
> built by Visual Studio 2010____
>
> __ __
>
> __ __
>
> __ __
>
> 2016-02-03 16:16 GMT+01:00 Yang Luo <hsluoyb@xxxxxxxxx
> <mailto:hsluoyb@xxxxxxxxx>>:____
>
> Hi list, ____
>
> __ __
>
> After several months, I retried updating wpcap project from VS 2005 to
> VS 2010) and encountered the same issue, under Wireshark 2.0.1 x64,
> Win10 x64.____
>
> __ __
>
> The Wireshark UI said "Child dumpcap process died: Access violation". I
> don't know what this means, because I have used Administrator privilege
> to launch Wireshark.____
>
> __ __
>
> I have just attached the x64 version wpcap.dll in this mail, you can
> just substitute it with the original WinPcap/Npcap version
> in C:\Windows\System32. Then launch Wireshark and you will see the
> crash. Hope that any one can see what's wrong with it here.____
>
> __ __
>
> Hi Yang,____
>
> I just gave a test to you dll (have replaced the existing version in
> C:\windows\System32\ and C:\windows\SysWOW64\ and did not face a crash
> when running it on Windows 7 x64:
>
> Version 2.0.2 (v2.0.2rc0-71-g1e10145 from master-2.0) ____
>
> __ __
>
> Copyright 1998-2016 Gerald Combs <gerald@xxxxxxxxxxxxx
> <mailto:gerald@xxxxxxxxxxxxx>> and contributors.____
>
> License GPLv2+: GNU GPL version 2 or later
> <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>____
>
> This is free software; see the source for copying conditions. There is
> NO____
>
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.____
>
> __ __
>
> Compiled (64-bit) with Qt 5.5.0, with WinPcap (4_1_3), with libz 1.2.8,
> with____
>
> GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with
> GnuTLS____
>
> 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with
> QtMultimedia,____
>
> with AirPcap.____
>
> __ __
>
> Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C,
> with____
>
> Npcap version 0.05, based on WinPcap version 4.1.3 (packet.dll version____
>
> 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
> with____
>
> GnuTLS 3.2.15, with Gcrypt 1.6.2, with AirPcap 4.1.0 build 1622.____
>
> Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (with SSE4.2), with 7879MB of
> physical____
>
> memory.____
>
> __ __
>
> __ __
>
> Built using Microsoft Visual C++ 12.0 build 40629____
>
> __ __
>
> Wireshark is Open Source Software released under the GNU General Public
> License.____
>
> __ __
>
> Check the man page and http://www.wireshark.org for more information.____
>
> __ __
>
> Does it require a reboot of the system?____
>
> Pascal.____
>
> __ __
>
> Cheers,____
>
> Yang____
>
> __ __
>
> __ __
>
> __ __
>
> On Wed, Aug 5, 2015 at 1:27 PM, Yang Luo <hsluoyb@xxxxxxxxx
> <mailto:hsluoyb@xxxxxxxxx>> wrote:____
>
> Hi list,____
>
> __ __
>
> The original WinPcap DLL, wpcap.dll is built by VS 2005, I have
> updated it to VS 2010 using VS automatic conversion wizard without
> changing one line of code. But when I launched Wireshark on Win8.1
> x64, I encountered an app crash error:____
>
> __ __
>
> -------------------------------------------------------------------------____
>
> Problem signature:____
>
> Problem Event Name: APPCRASH____
>
> Application Name: dumpcap.exe____
>
> Application Version: 1.99.9.58____
>
> Application Timestamp: 55be9e4d____
>
> Fault Module Name: wpcap.dll____
>
> Fault Module Version: 0.3.0.727____
>
> Fault Module Timestamp: 55c19749____
>
> Exception Code: c0000005____
>
> Exception Offset: 000000000001fbca____
>
> OS Version: 6.3.9600.2.0.0.256.4____
>
> Locale ID: 1033____
>
> Additional Information 1: 12c1____
>
> Additional Information 2: 12c1dabe3a9c9d7be788f03210b25196____
>
> Additional Information 3: b207____
>
> Additional Information 4: b207cb8de8ff9d2641379d976acebfca____
>
> __ __
>
> Read our privacy statement online:____
>
> http://go.microsoft.com/fwlink/?linkid=280262____
>
> __ __
>
> If the online privacy statement is not available, please read our
> privacy statement offline:____
>
> C:\Windows\system32\en-US\erofflps.txt____
>
> -------------------------------------------------------------------------____
>
> __ __
>
> I have updated Packet.dll from VS 2005 to VS 2010 without problem.
> (If I use VS 2005 version wpcap.dll and VS 2010 version Packet.dll,
> it works fine) So it can't be lacking C run-time issue. I don't
> know what's wrong with it?____
>
> __ __
>
> __ __
>
> Cheers,____
>
> Yang____
>
> __ __
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list
> <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx
> <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe____
>
> __ __
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
> <mailto:wireshark-dev@xxxxxxxxxxxxx>>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx
> <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
>
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
