Mbed Stats: Assert if NULL pointer passed as arg

[deepikabhavnani]

Description

Check for NULL pointer before access to any parameter. API arguments must be verified before access.

Pull request type

[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 1930
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6809/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Test : SUCCESS

Build number : 1752
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/6809/1752

[mbed-ci]

Exporter Build : FAILURE

Build number : 1576
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6809/

[cmonr]

@studavekar Not sure if you're tracking this, but the failed exporter build job failed with symbols being multiply defined.

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 1585
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6809/

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 1590
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6809/

[deepikabhavnani]

Build number : 1590

@cmonr @studavekar - No failure artifacts

[cmonr]

@deepikabhavnani Correct. In this particular instance, looks like Jenkins borked:

java.io.EOFException> 07:09:08 FATAL: command execution failed
07:09:08 java.io.EOFException
07:09:08 	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2675)
07:09:08 	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3150)
07:09:08 	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:859)
07:09:08 	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:355)
07:09:08 	at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
07:09:08 	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
07:09:08 	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
07:09:08 Caused: java.io.IOException: Unexpected termination of the channel
07:09:08 	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

Annoying that it's happened twice in a row... It's an ongoing issue we've been trying to root cause.
/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 1596
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6809/

[cmonr]

Restarting again since modifications to CI were made.
/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1604
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6809/