Wireshark-bugs: [Wireshark-bugs] [Bug 11839] Starting Wireshark from Visual Studio 2013 gives Sy
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 01 Dec 2015 16:35:57 +0000

Comment # 3 on bug 11839 from 
I don't know if this helps, or if you already know this, but this is what
happens:

Wireshark is running and spawns a process to run gspawn-win64-helper.exe

The stack at the process start looks like this:

.
.
9    msvcrt.dll    wspawnvpe + 0x98    0x7fefe745260   
C:\Windows\system32\msvcrt.dll
10    libglib-2.0-0.dll    g_spawn_error_quark + 0xcb3    0x68637a43   
C:\Development\Wireshark\build\run\Debug\libglib-2.0-0.dll
11    libglib-2.0-0.dll    g_spawn_sync_utf8 + 0x15c    0x6863816c   
C:\Development\Wireshark\build\run\Debug\libglib-2.0-0.dll
12    Wireshark.exe    extcap_foreach + 0x2f1,
c:\development\wireshark\extcap.c(194)    0x13f24ec61   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
13    Wireshark.exe    extcap_interface_list + 0xa5,
c:\development\wireshark\extcap.c(357)    0x13f24da75   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
14    Wireshark.exe    capture_interface_list + 0x82,
c:\development\wireshark\capchild\capture_ifinfo.c(125)    0x13f673922   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
15    Wireshark.exe    scan_local_interfaces + 0x1e5,
c:\development\wireshark\ui\iface_lists.c(113)    0x13f6466a5   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
16    Wireshark.exe    fill_in_local_interfaces + 0x53,
c:\development\wireshark\ui\iface_lists.c(405)    0x13f646433   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
17    Wireshark.exe    main + 0x119d,
c:\development\wireshark\wireshark-qt.cpp(1184)    0x13f2377ed   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
18    Wireshark.exe    WinMain + 0xed,
c:\work\build\qt5_workdir\w\s\qtbase\src\winmain\qtmain_win.cpp(112)   
0x13f68afed    C:\Development\Wireshark\build\run\Debug\Wireshark.exe
19    Wireshark.exe    __tmainCRTStartup + 0x271,
f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c(607)    0x13f6894d1   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
20    Wireshark.exe    WinMainCRTStartup + 0xe,
f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c(465)    0x13f68924e   
C:\Development\Wireshark\build\run\Debug\Wireshark.exe
21    kernel32.dll    BaseThreadInitThunk + 0xd    0x76c05a4d   
C:\Windows\system32\kernel32.dll
22    ntdll.dll    RtlUserThreadStart + 0x1d    0x76e3b831   
C:\Windows\SYSTEM32\ntdll.dll

gspawn-win64-helper.exe then spanws a process to run androiddump.exe

The command line for this is:

C:\\Development\\Wireshark\\build\\run\\Debug\\extcap\\androiddump.exe
--extcap-interfaces

During execution, androiddump.exe tries to open
C:\Development\Wireshark\build\run\Debug\extcap\wiretap-2.1.0-TmSyncro.dll

It then tries to open the file across my whole search path and of course
doesn't find it.

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