[pgt, 11/30/95]
In java/src/solaris/java/runtime/socket.c:
The java_net_DatagramSocket_datagramSocketBind function sets
the localPort field in network-byte-order (which is the form that
getsockname(3N) returns it in). It should probably set it in host-byte-order.
The java_net_DatagramSocket_datagramSocketPeek function also
returns the port number in network-byte-order instead of host-byte-order.
It also converts the remote_addr to network-byte-order, although
remote_addr is already in network-byte-order (recvfrom(3n) will
return the address of the received packet in network-byte-order).
The same mistake is repeated in the java_net_DatagramSocket_datagramSocketReceive
function.
In java/src/solaris/java/runtime/socket.c:
The java_net_DatagramSocket_datagramSocketBind function sets
the localPort field in network-byte-order (which is the form that
getsockname(3N) returns it in). It should probably set it in host-byte-order.
The java_net_DatagramSocket_datagramSocketPeek function also
returns the port number in network-byte-order instead of host-byte-order.
It also converts the remote_addr to network-byte-order, although
remote_addr is already in network-byte-order (recvfrom(3n) will
return the address of the received packet in network-byte-order).
The same mistake is repeated in the java_net_DatagramSocket_datagramSocketReceive
function.