Hi Greg,
>
> Where do you see a problem in this?
>
I found that 2 tasks can race calling up_schedule_sigaction to set the
sigdeliver in TCB.
In up_schedule_sigaction , a critical section should prevent this from
happening.
However, If the calling task suspends voluntary, e.g. by calling
syslog, a
Hi,
I noticed that both the armv7m and x86 port of nuttx's signal sending
procedure cannot handle nested signals.
I am wondering that in the up_sigdeliver functions.
A task A, being signaled, is possibile to be switch-out because of
1. calling syslog via sinfo
2. interrupts
A newly switche
Hi,
I noticed that both the armv7m and x86 port of nuttx's signal sending
procedure cannot handle nested signals.
I am wondering that in the up_sigdeliver functions.
A task A, being signaled, is possibile to be switch-out because of
1. calling syslog via sinfo
2. interrupts
A newly switched in
