open_issues/fork_deadlock: Data I collected.

[hurd-web.git] / open_issues / code_analysis.mdwn

diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index 8c604e3..14e8214 100644 (file)
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -37,11 +37,6 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
         specifiers, and have it emit useful warnings in case these are pointing
         to uninitialized data (for *in* only).
 
-  * [[Port Sequence Numbers|microkernel/mach/ipc/sequence_numbering]].  If
-    these are used, care must be taken to update them reliably, [[!message-id
-    "1123688017.3905.22.camel@buko.sinrega.org"]].  This could be checked by a
-    static analysis tool.
-
   * [[!wikipedia List_of_tools_for_static_code_analysis]]
 
   * [Engineering zero-defect software](http://esr.ibiblio.org/?p=4340), Eric
@@ -91,6 +86,16 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
   * [Coverity](http://www.coverity.com/) (nonfree?)
 
 
+## Hurd-specific Applications
+
+  * [[Port Sequence Numbers|microkernel/mach/ipc/sequence_numbering]].  If
+    these are used, care must be taken to update them reliably, [[!message-id
+    "1123688017.3905.22.camel@buko.sinrega.org"]].  This could be checked by a
+    static analysis tool.
+
+  * [[glibc]]'s [[glibc/critical_section]]s.
+
+
 # Dynamic
 
   * [[community/gsoc/project_ideas/Valgrind]]