Hi Xiang, I've checked https://github.com/apache/incubator-nuttx/pull/354 PR. It fixed issues it supposed to fix, thanks.
But I've still have semaphore assertion running test case WakeBlockingConnectMultiThread in do_wake_test() on third call in loop of sem_post(&tid_releasesem) when tidx is 2. (examples/usrsocktest/usrsocktest_wake_with_signal.c:515) [image: изображение.png] As I understand, you do not have such issue, so it's looks like reason is totally somewhere in my configuration. Especially due to fact that, as I wrote, I'm playing with it on Windows inside px4 project on my custom board with stm32f405, using latest original nuttx and apps. I had tried to increase twice CONFIG_EXAMPLES_USRSOCKTEST_STACKSIZE, it didn't help, assertion in the same place. сб, 22 февр. 2020 г. в 18:11, Xiang Xiao <[email protected]>: > The semaphore assertion look like the memory corrruption(maybe the > stack too small) which platform you are running. > > On Sat, Feb 22, 2020 at 6:52 PM Oleg Evseev <[email protected]> wrote: > > > > Hi Xiang, > > > > I can check it only on Monday, thanks! > > > > But, by the way, in commits you mentioned several errors in usrsocktest > > that looks different than on my first screenshot (especially debug > > assertion failed somewhere inside semaphore). Maybe there will still be > > problems due to my wrong settings. Will see after checking this PR. > > In any case, thanks for your time and support! > > > > сб, 22 февр. 2020 г. в 13:38, Xiang Xiao <[email protected]>: > > > > > Oleg, try this PR: > > > https://github.com/apache/incubator-nuttx/pull/354 > > > with Masayuki and my patch, all test in usrsocktest should pass now. > > > Actually, all fail is very minor: > > > 1.Set the different errno > > > 2.Foget to check NULL pointer > > > 3.Don't zero the sockaddr padding bytes > > > ,usrsock work well very even without these patch. >
