jirentabu / crashrpt

Automatically exported from code.google.com/p/crashrpt
0 stars 0 forks source link

CrashSender doesn't work on Windows 2000 #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1.  Run CrashSender.exe from a Windows 2000 command prompt

The following error message is displayed:

"The procedure entry point freeaddrinfo could not be located in the synamic 
link library WS2_32.dll"

Original issue reported on code.google.com by robert.c...@gmail.com on 8 Mar 2010 at 3:40

GoogleCodeExporter commented 9 years ago
Requirements for freeaddrinfo are Windows 2000 Professional, Windows 2000 
Server or
later. So in theory it should be there. 

But, as MSDN says "The FreeAddrInfoW  function is the Unicode version of
freeaddrinfo. The FreeAddrInfoW function was added to the Ws2_32.dll  in 
Windows XP
with Service Pack 2 (SP2). The FreeAddrInfoW  function cannot be used on 
versions of
Windows earlier than Windows XP with SP2."

I suppose this problem is related to FreeAddrInfoW.

Original comment by zexspect...@gmail.com on 9 Mar 2010 at 5:42

GoogleCodeExporter commented 9 years ago
Oops.. I missed this piece of text "To execute an application using this 
function on
earlier versions of Windows (Windows 2000, Windows NT, and Windows Me/98/95), 
then
you must include the Ws2tcpip.h file and also include the Wspiapi.h  file. When 
the
Wspiapi.h include file is added, the freeaddrinfo  function is defined to the
WspiapiFreeAddrInfo inline function in the Wspiapi.h  file. At runtime, the
WspiapiFreeAddrInfo function is implemented in such a way that if the 
Ws2_32.dll or
the Wship6.dll (the file containing freeaddrinfo in the IPv6 Technology Preview 
for
Windows 2000) does not include freeaddrinfo, then a version of freeaddrinfo is
implemented inline based on code in the Wspiapi.h header file. This inline code 
will
be used on older Windows platforms that do not natively support the freeaddrinfo
function."

http://msdn.microsoft.com/en-us/library/ms737931%28VS.85%29.aspx

I think this issue can be fixed by including those headers.

Original comment by zexspect...@gmail.com on 9 Mar 2010 at 6:12

GoogleCodeExporter commented 9 years ago
That does the trick.  Thanks!

Original comment by robert.c...@gmail.com on 9 Mar 2010 at 4:25

GoogleCodeExporter commented 9 years ago
Fixed in v.1.2.2

Original comment by zexspect...@gmail.com on 23 Mar 2010 at 5:36