https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #11 from Jaap Keuter ---
Is there anything more to do for this bug?
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #10 from Gerald Combs ---
(In reply to Guy Harris from comment #8)
> For what it's worth, dumpcap calls WSAStartup() twice - once, in main(),
> with version 1.1, and once, in capture_loop_open_input(), with version 2.2.
>
> Pe
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #9 from Guy Harris ---
Here's libpcap's DllMain:
BOOL WINAPI DllMain(
HANDLE hinstDLL,
DWORD dwReason,
LPVOID lpvReserved
)
{
return (TRUE);
}
I'm not seeing how that calls any Winsock API.
And the stack trace
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #8 from Guy Harris ---
For what it's worth, dumpcap calls WSAStartup() twice - once, in main(), with
version 1.1, and once, in capture_loop_open_input(), with version 2.2.
Perhaps we should call it in main() with version 2.2,
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #7 from Gerald Combs ---
(In reply to Guy Harris from comment #6)
> Just for fun, what happens if you run it on a system without WinPcap or
> Npcap installed? They also have to do socket stuff for 1) name resolution
> in pcap_
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #6 from Guy Harris ---
Just for fun, what happens if you run it on a system without WinPcap or Npcap
installed? They also have to do socket stuff for 1) name resolution in
pcap_compile() and 2) at least for WinPcap, remote cap
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #5 from Gerrit Code Review ---
Change 33033 had a related patch set uploaded by Gerald Combs:
Windows: Modernize our WSAStartup usage.
https://code.wireshark.org/review/33033
--
You are receiving this mail because:
You are w
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #4 from Gerald Combs ---
(In reply to Gerald Combs from comment #3)
> However, if I add it to epan/epan.c at the top of epan_init or
> epan/addr_resolv.c just before the ares_init calls an exception is triggered
> at WSAGetLas
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #3 from Gerald Combs ---
Running Wireshark under Application Verifier here gives me the following log:
A Winsock API was called before a
successful WSAStartup() or after
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #2 from Tomasz Mon ---
(In reply to Jaap Keuter from comment #1)
> Could that tool show what path is taken to get to host_name_lookup_init()
> before WSAStartup() is called?
No, however I placed at breakpoint in ui/qt/main.cpp
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15711
--- Comment #1 from Jaap Keuter ---
The paths to host_name_lookup_init() I could find were from ui/qt/main.cpp,
which all came _after_
#ifdef _WIN32
/* Start windows sockets */
result = WSAStartup( MAKEWORD( 1, 1 ), &wsaData );
11 matches
Mail list logo
