From: Julian Seward <jseward@acm.org>
Date: Fri, 24 May 2002 00:00:59 +0000 (+0000)
Subject: Comment-only change: add a list of known problems with the signal simulator.
X-Git-Tag: svn/VALGRIND_1_0_3~147
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7584993246d239bdbc7fcb5f891b38cec62030e9;p=thirdparty%2Fvalgrind.git

Comment-only change: add a list of known problems with the signal simulator.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@319
---

diff --git a/coregrind/vg_signals.c b/coregrind/vg_signals.c
index 9acf74f60b..7a8c737e04 100644
--- a/coregrind/vg_signals.c
+++ b/coregrind/vg_signals.c
@@ -39,6 +39,25 @@
 #define DEBUG_SIGNALS
 
 
+/* KNOWN BUGS 24 May 02:
+
+   - A signal is not masked in its own handler.  Neither are the
+     signals in the signal's blocking mask.
+
+   - There is only one pending set for the entire process, whereas
+     POSIX seems to require each thread have its own pending set.
+     This means that a signal can only be pending for one thread at
+     a time.
+
+   - The following causes an infinite loop: start Hugs, Feb 2001 
+     version, and do Control-C at the prompt.  There is an infinite
+     series of sigints delivered (to the client); but also seemingly
+     to valgrind, which is very strange.  I don't know why.
+
+   Probably a lot more bugs which I haven't discovered yet.
+*/
+
+
 /* ---------------------------------------------------------------------
    Forwards decls.
    ------------------------------------------------------------------ */
diff --git a/vg_signals.c b/vg_signals.c
index 9acf74f60b..7a8c737e04 100644
--- a/vg_signals.c
+++ b/vg_signals.c
@@ -39,6 +39,25 @@
 #define DEBUG_SIGNALS
 
 
+/* KNOWN BUGS 24 May 02:
+
+   - A signal is not masked in its own handler.  Neither are the
+     signals in the signal's blocking mask.
+
+   - There is only one pending set for the entire process, whereas
+     POSIX seems to require each thread have its own pending set.
+     This means that a signal can only be pending for one thread at
+     a time.
+
+   - The following causes an infinite loop: start Hugs, Feb 2001 
+     version, and do Control-C at the prompt.  There is an infinite
+     series of sigints delivered (to the client); but also seemingly
+     to valgrind, which is very strange.  I don't know why.
+
+   Probably a lot more bugs which I haven't discovered yet.
+*/
+
+
 /* ---------------------------------------------------------------------
    Forwards decls.
    ------------------------------------------------------------------ */