1. EXW crash on XP for winsock.ew
- Posted by s6263 at sg.edu.tr
Mar 02, 2002
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01C1C196.5864A2D0
charset="iso-8859-9"
Why i am getting an EXW.EXE crash when i run a program
which includes winsock.ew on win XP home edition???
the WsockInit() is done sucessfully but when anyother function is called the
program crashes...
Deniz Dizman
------=_NextPart_000_0007_01C1C196.5864A2D0
charset="iso-8859-9"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-9">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Why i am getting an EXW.EXE crash when i run a
program</FONT></DIV>
<DIV><FONT face=Arial size=2>which includes winsock.ew on win XP home
edition???</FONT></DIV>
<DIV><FONT face=Arial size=2>the WsockInit() is done sucessfully but when
anyother function is called the program crashes...</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Deniz Dizman</FONT></DIV>
------=_NextPart_000_0007_01C1C196.5864A2D0--
2. Re: EXW crash on XP for winsock.ew
Deniz Dizman writes:
> Why i am getting an EXW.EXE crash when i run a program
> which includes winsock.ew on win XP home edition???
> the WsockInit() is done sucessfully but when anyother function is called the
> program
crashes...
winsock.ew as is has some bugs:
At two places it incorrectly tries to free() a hostent structure.
one place is:
free(host)
in WsockGetIP()
another place is:
free(phostent)
in WsockHostInfo()
Or maybe the winsock.dll for XP is somehow incompatible ?
Martin
3. Re: EXW crash on XP for winsock.ew
> Why i am getting an EXW.EXE crash when i run a program
> which includes winsock.ew on win XP home edition???
> the WsockInit() is done sucessfully but when anyother function is called the
> program crashes...
> Deniz Dizman
I had some problems with a modified version of winsock.ew that I
traced back the use of both WinAPI and Euphoria memory handling
routines together...
I replaced all the memory allocation, peeking and pokeing stuff with
Euphoria's own routines and it seemed to clear up the memory
problems...
I'd try the original winsock.ew but the link in the archives seems to
be broken.
Thomas Parslow (PatRat)
E-Mail/Jabber: tom at almostobsolete.net
ICQ: 26359483
