[#EXT_EP-9639] Incorrect assert fires if SlNetIfNDK_recvFrom() is passed MSG

[EXT_EP-9639] Incorrect assert fires if SlNetIfNDK_recvFrom() is passed MSG_DONTWAIT Created: 10/Feb/20 Updated: 19/Feb/20 Resolved: 14/Feb/20
Status:	Fixed
Project:	Embedded Software & Tools
Component/s:	None
Affects Version/s:	None
Fix Version/s:	None

Type:

Bug

Priority:

Medium

Reporter:

TI User

Assignee:

TI User

Resolution:

Fixed

Votes:

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Product:

Network Development Kit

Internal ID:

NDK-469

Found In Release:

NDK_3_60_00

Fix In Release:

NDK_3_75_00

Description

See E2E post: https://e2e.ti.com/support/processors/f/791/t/834640#pi320966=3

NDK_recvfrom() will return an error if MSG_DONTWAIT is passed and no data is ready. SockRecv() is ultimately called in this path and that will exit with an error without filling in the sockaddr struct if MSG_DONTWAIT is used and no data is ready for the socket.

SlNetIfNDK_recvFrom() checks the sockaddr struck BEFORE checking the return code of NDK_recvfrom(), and will thus cause an assert to be fired.

SlNetIfNDK_recvFrom() should check the return value first, and return with an error if there is an issue.

Generated at Sat Dec 13 11:32:49 CST 2025 using Jira 10.3.7#10030007-sha1:a563685562f94d165eb4e158cfb2a142338d8c54.

[EXT_EP-9639] Incorrect assert fires if SlNetIfNDK_recvFrom() is passed MSG_DONTWAIT Created: 10/Feb/20 Updated: 19/Feb/20 Resolved: 14/Feb/20