summaryrefslogtreecommitdiff
path: root/nuttx/ChangeLog
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2013-01-13 18:53:00 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2013-01-13 18:53:00 +0000
commit0191f2d9e4a4c9857ee37655dd3da523cf74a48a (patch)
treedf530299e0171e8a86a2709ed4f19a1468efda4e /nuttx/ChangeLog
parent0d8a269d4bbb18fa509e642ae2eaec8a8c80a1c3 (diff)
downloadnuttx-0191f2d9e4a4c9857ee37655dd3da523cf74a48a.tar.gz
nuttx-0191f2d9e4a4c9857ee37655dd3da523cf74a48a.tar.bz2
nuttx-0191f2d9e4a4c9857ee37655dd3da523cf74a48a.zip
Use SIGCHLD with waitpid(); implemented wait() and waitid()
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5515 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/ChangeLog')
-rw-r--r--nuttx/ChangeLog7
1 files changed, 7 insertions, 0 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index 7deb9fa94..e8d4f7309 100644
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -3922,3 +3922,10 @@
which decrements the lockcount on the wrong TCB. The failure case
that I saw was that pre-emption got disabled in the IDLE thread,
locking up the whole system.
+ * sched/sched_waitpid.c: Use SIGCHLD instead of a semaphore. This
+ is a much more spec-compliant implemenation. However, there are
+ some issues with overruning signals because NuttX does not support
+ queueing of signals (POSIX does not require it). I think it may
+ need to.
+ * sched/sched_waitid.c and sched_wait.c: Add support for waitid()
+ and wait(). See issues with waitpid() above.