|
From: <sv...@va...> - 2009-04-29 03:40:22
|
Author: njn
Date: 2009-04-29 04:40:08 +0100 (Wed, 29 Apr 2009)
New Revision: 9670
Log:
Convert Darwin-specific "FIXME" comments to "DDD" comments to make them
easier to count.
Modified:
branches/DARWIN/coregrind/m_syswrap/syswrap-darwin.c
branches/DARWIN/coregrind/m_syswrap/syswrap-x86-darwin.c
Modified: branches/DARWIN/coregrind/m_syswrap/syswrap-darwin.c
===================================================================
--- branches/DARWIN/coregrind/m_syswrap/syswrap-darwin.c 2009-04-29 02:04:57 UTC (rev 9669)
+++ branches/DARWIN/coregrind/m_syswrap/syswrap-darwin.c 2009-04-29 03:40:08 UTC (rev 9670)
@@ -2352,7 +2352,7 @@
void*, file_actions, char**, argv, char**, envp );
PRE_MEM_WRITE("posix_spawn(pid)", ARG1, sizeof(vki_pid_t) );
PRE_MEM_RASCIIZ("posix_spawn(path)", ARG2);
- //FIXME: check file_actions
+ // DDD: check file_actions
if (ARG4 != 0)
pre_argv_envp( ARG4, tid, "posix_spawn(argv)",
"posix_spawn(argv[i])" );
@@ -2486,7 +2486,7 @@
vg_assert(j == tot_args+1);
}
- /* XXXX JRS FIXME: sort out the signal state. What signal
+ /* DDD: sort out the signal state. What signal
state does the child inherit from the parent? */
if (0) {
Modified: branches/DARWIN/coregrind/m_syswrap/syswrap-x86-darwin.c
===================================================================
--- branches/DARWIN/coregrind/m_syswrap/syswrap-x86-darwin.c 2009-04-29 02:04:57 UTC (rev 9669)
+++ branches/DARWIN/coregrind/m_syswrap/syswrap-x86-darwin.c 2009-04-29 03:40:08 UTC (rev 9670)
@@ -484,7 +484,7 @@
thread_wrapper which acquires the lock before continuing.
Let's hope nothing non-thread-local happens until that point.
- FIXME: I think this is plain wrong .. if we get to
+ DDD: I think this is plain wrong .. if we get to
thread_wrapper not holding the lock, and someone has recycled
this thread slot in the meantime, we're hosed. Is that
possible, though? */
|