Details
Description
When an application creates a TCP protocol based socket and this socket is connected to a peer using the Connect API, the status callback passed to this api function will not be called in certain situations. E.g. when trying to connect with a non-existent peer.
It is expected that the status/error callback is invoked for any asynchronous error on the socket.
Attachments
Issue Links
- blocks
-
PSLWIP-346 Wrong behavior of GetSockOpt for SO_ERROR
- Closed
-
PSPNSV5-296 Upgrade LwIP based IP stack to V4.4.0.3
- Closed
- discovered by
-
PSLWIP-346 Wrong behavior of GetSockOpt for SO_ERROR
- Closed