Please provide a short, self-contained sample (see the bug's do's and don'ts).

Here is a small example of script ...

if (($sock = socket_create (AF_INET, SOCK_STREAM, 0)) < 0) {
  echo "socket_create() failed: reason: " . socket_strerror ($sock) . "\n";
}
if (($ret = socket_bind ($sock, '127.0.0.1', 10000)) < 0) {
  echo "socket_bind() failed: reason: " . socket_strerror ($ret) . "\n";
}

PHP crashes here, on the socket_bind command.
This script was found on the page about the socket functions. I've downloaded the last RC version but it also crashes.
I have the window's dialog with 'Close', 'Debug' or 'Deltails >>' ...

The category has changed to PDF functions (I made a mistake while filling the form ?? ).
Changing back to 'Socket related' ...

Ok, I can't reproduce this on w2k (I don't have a w98 system to test).

First, try if it works on w2k for you. If it works, we know it's w98 system problem and we can dig furhter into that direction.

Second, your return checking's aren't very good. socket_create() returns either resource or false, but not something which we would say is '< 0'.

The same for socket_bind(), it returns an boolean, true or false, nothing else.

(that's from the source, the documentation on php.net is outdated as there have been recent changes to the sources).

This problem doesn't happens on w2k ...
It's w9x specific problem (win95 is also concerned).

PS: My test code was found in the documentation. I've updated my code ...
PS2: I'll look in the source and do some tries to find a way to fix this bug (I have VC++, I could use another compiler but I have only this one).

I know it's a bind error and if the IP is changed to "" no error happens ...

The CSV version doesn't include this bug anymore.

Just one more thing : socket_bind() returns '' on success ...

Oops !!
I made an error, socket_bind returns 1 on success.
True = -1

Wait, did you test with CVS now?!

It's supposed to ONLY return boolean false or true (from reading the source code).

Can you verify this too please.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

win98 will crash if you bind_socket your IP to other than yourself - IP cant be 127.0.0.1 either

This looks more like a socket_strerror() problem that was addressed recently, as the legacy winsock(1.1) doesn't report a correct errno when bind() fails according to http://www.sockets.com/err_lst1.htm,

----------------------------------------------------------------------------
WSAEADDRNOTAVAIL (10049) Cannot assign requested address. 

Berkeley description: Normally results from an attempt to create a socket with an address not on this machine. 

WinSock description: Partly the same as Berkeley. The "address" it refers to is the remote socket name (protocol, port and address). This error occurs when the sin_port value is zero in a sockaddr_in structure for connect() or sendto(). 

In Berkeley, this error also occurs when you are trying to name the local socket (assign local address and port number) with bind(), but Windows Sockets doesn't ascribe this error to bind(), for some unknown reason. 

Developer suggestions: Assume bind() will fail with this error. Let the network system assign the default local IP address by referencing INADDR_ANY in the sin_addr field of a sockaddr_in structure input to bind(). Alternately, you can get the local IP address by calling gethostname() followed by gethostbyname(). 

WinSock functions: connect(), sendto(), FD_CONNECT 

Additional functions: It seems odd that the v1.1 specification doesn't ascribe this error to the function bind().

----------------------------------------------------------------------------