jkivilin commented on issue #24: Fix wait loop and void cast
URL: https://github.com/apache/incubator-nuttx/pull/24#issuecomment-572118244
 
 
   With 6a3c2ad reverted and 
https://github.com/apache/incubator-nuttx/commit/a5aac1fd5515e2447785025da4102c5b04fc6389.patch
 applied, usrsocktest output is the same (so problem is not with in a5aac1fd55):
   ```
   $ ./nuttx 
   
   NuttShell (NSH) NuttX-8.2
   MOTD: username=admin password=Administrator
   nsh> usrsocktest
   Starting unit-tests...
   Testing group "CharDev" =>
           Group "CharDev": [OK]
   Testing group "NoDaemon" =>
           Group "NoDaemon": [OK]
   Testing group "BasicDaemon" =>
           Group "BasicDaemon": [OK]
   Testing group "BasicConnect" =>
           Group "BasicConnect": [OK]
   Testing group "BasicConnectDelay" =>
           Group "BasicConnectDelay": [OK]
   Testing group "NoBlockConnect" =>
           Group "NoBlockConnect": [OK]
   Testing group "BasicSend" =>
           Group "BasicSend": [OK]
   Testing group "NoBlockSend" =>
           Group "NoBlockSend": [OK]
   Testing group "BlockSend" =>
           Group "BlockSend": [OK]
   Testing group "NoBlockRecv" =>
           [TEST ASSERT FAILED!]
                   In function "Receive":
                   line 200: Assertion `memcmp((&remoteaddr), (&addr), 
(addrlen)) == 0' failed.
           Group "NoBlockRecv": [FAILED]
   Testing group "BlockRecv" =>
           [TEST ASSERT FAILED!]
                   In function "NoBlockConnect":
                   line 268: Assertion `memcmp((&remoteaddr), (&addr), 
(addrlen)) == 0' failed.
           Group "BlockRecv": [FAILED]
   Testing group "RemoteDisconnect" =>
           Group "RemoteDisconnect": [OK]
   Testing group "BasicSetSockOpt" =>
           Group "BasicSetSockOpt": [OK]
   Testing group "BasicGetSockOpt" =>
           Group "BasicGetSockOpt": [OK]
   Testing group "BasicGetSockName" =>
   Segmentation fault (core dumped)
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to