wangchdo commented on PR #17352: URL: https://github.com/apache/nuttx/pull/17352#issuecomment-3573461071
> 1. Okay I can see the @xiaoxiang781216 point, the "partial signal handling" is equivalent to disabling signals but least invasive to the current code. Full signal disable may be breaking existing code, but may result in smaller code? Lets discuss on the mailing list please before anything is merged - all pros and cons of both solutions I am sure we will find good way forward together maybe even something new :-) > 2. I agree fully with @acassis that we clearly miss the Xiaomi roadmap and sometimes we are surprised by incoming changes. I have created this dedicated "Project" where Xiaomi can put Issues and mark timeline. This will also clearly show Xiaomi support to NuttX and maybe motivate other companies to help us! @xiaoxiang781216 is the admin/manager of that app. It is called "Project" and its kind of sub-application here in GitHub it works on the existing Issues and PR just to organize them so its just king of organizer with a timeline plot and list of tasks/issues :-) > > https://github.com/orgs/apache/projects/551 As @anchao mentioned, which I agree a lot: sigals are disabled not only for footprint but also for improving safety: To reiterate, the current implementation of signals is highly unsafe because it borrows the context of the interrupted thread in its delivery logic. If a lock is held in the signal context, a serious bug will occur, which is why we prohibit the use of signals. -- 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]
