xiaoxiang781216 commented on PR #6197: URL: https://github.com/apache/incubator-nuttx/pull/6197#issuecomment-1119389154
> > Yes, it's the final target. The major block issue is that kernel space may trigger the termination proactively in some special case: > > ``` > > 1. signal process > > > > 2. cancelation point > > ``` > > ``` > The atexit() function registers the given function to be calledat normal process termination, > either via [exit(3)](https://man7.org/linux/man-pages/man3/exit.3.html) or via return from the program's > main(). Functions so registered are called in the reverse order of their registration; > no arguments are passed. > ``` > > I don't think the exit functions are called on unexpected termination. Please search exit/terminate in sched, you can find them. > Will signal process or cancellation point call exit() ? Yes, it's in the current code base, but it's wrong for kernel/protected. > In this case should it call the userspace libc version of exit() or the kernelspace version ? the userspace api but call in kernel context. -- 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: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
