TimJTi commented on issue #12629: URL: https://github.com/apache/nuttx/issues/12629#issuecomment-2218002955
> Hi @TimJTi I suggest you to create some blog post about it. If you faced this issue and wasted time with it, other people could have some issue. Think how you can help to avoid other people feeling the same pain. @acassis I would agree with you, in principle, but I think the bug I had was down to my inexperience as I learn how to write acceptable App code for NuttX! I can't 100% be sure exactly what the bug was as I found quite a few issues as I switched between full and supressed optimization, and from running the app from nsh or as the startup app. But my strong feeling is that the default setup while I am developing (supressed optimization), even running as the startup app, slowed down the creation of my threads enough for the code to "get away" with trying to read data from a queue and send signals, as the thread wanting the data was running - but the PR "blamed" here sped up the thread starting enough to reveal the problem. But it might have been something else LOL. A code review from an experienced POSIX/LINUX developer would have found it I'm sure...but I am learning on the job here and on my own!!!! I should have stuck to bare metal.....sigh!!!!!!!! -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
