Quantcast
Channel: Forum - Recent Threads
Viewing all articles
Browse latest Browse all 5781

Incoherent SO_RCVTIMEO behavior

$
0
0

Hi,

Using the SSP 1.4.0 for a S7G2DK board I stumbled upon a strange behavior in NetX. I can totally call setsockopt to set the SO_RCVTIMEO option of a socket to 0, meaning that the socket would block indefinitely according to the standard BSD setup. But when I call getsockopt to read the SO_RCVTIMEO option, if nx_bsd_option_receive_timeout is set to 0 a NX_SOC_ERROR is returned with the errno EINVAL.

 

Why is it so? Is it a typo? Shouldn't I be able to read a 0 as the receive timeout option value for a socket?

 

Best regards,

Bastien


Viewing all articles
Browse latest Browse all 5781

Trending Articles