Mbed os 5.11.0 oob: fix fault exception issue

[tz-arm]

Description

Fix the fault exception issue in socket_recvfrom().
It is caused by the usage of null pointer as SocketAddress *addr.
e.g. socket_recv() -> socket_recvfrom(handle, NULL, data, size);

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

[ciarmcom]

@tz-arm, thank you for your changes.
@ARMmbed/mbed-os-wan @ARMmbed/mbed-os-maintainers please review.

[adbridge]

@AnttiKauppila @AriParkkila As this seems to only be affecting one target I am marking this 5.11.1

[tz-arm]

@adbridge a little confused about "only be affecting one target", could you share more why it is relevant to target? thanks.

[cmonr]

@adbridge Am confused by the statement as well.

The original issue was reported with a single target, but the fix is considerably more generic. Moved to RC3, and will let the eastern hemisphere sort it out.

@tz-arm This PR still needs work. Please take a look at the travis-ci/astyle job output for details. Small whitespace/styling issues were found with the PR.

[jarvte]

Just fix astyle.

[AriParkkila]

Please run:
astyle.exe -n --options=.astylerc features/cellular/framework/AT/AT_CellularStack.cpp

[tz-arm]

@cmonr @adbridge @AriParkkila, thanks for your comments, I understand where the target confusion come from:
While I see " What target does this relate to" from issue report format, normally I will fill the target I used for testing/reproduce, but not the target I assume it will affect (reporter could not always point out the affect targets correctly), is it possible to make the comments more clear? e.g. reproduce target, affect target

[0xc0170]

The report was fine (reported target that you tested on, the bug was found in the generic layer)

[0xc0170]

Test restarted (failed due to not enough space , fixed now)

[mbed-ci]

Test run: FAILED

Summary: 2 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test
• jenkins-ci/mbed-os-ci_exporter

[cmonr]

Last CI job somehow got stuck at starting the exporter jobs, even though CI was completely empty.

Restarted jenkins-ci/exporter job.

Because original job was never started, there was nothing to restart. Had to manually fill in job parameters. On success, should make continuous-integration/jenkins/pr-head green as well.