Fix wrong get socket error method

[martin-kuhn]

Description

During network tests we found out, that using SOCK_getlasterror() instead of SOCK_getsocklasterror() leads to an infinite loop when a remote client closes the network socket unexpectedly. Hence the watchdog will not be fed anymore and it will trigger a reset.

How Has This Been Tested?

This has been tested on a custom STM32F427 based MCU board with network capabilities.

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Signed-off-by: Martin Kuhn [email protected]

[nfbot]

Hi @martin-kuhn,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

[josesimoes]

LGTM!