summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-11-24 09:59:55 +0100
committerThomas Schwinge <thomas@schwinge.name>2011-11-24 09:59:55 +0100
commitfc08486fd989e724bd8df4a086d453612c4f2aba (patch)
treec32d65775e3f2c2589354ff21cd15531755d29db /open_issues
parent26d86a6a7e67e81ae5d02bfdb0d4363f2e741baa (diff)
open_issues/code_analysis: Static code checker for port sequence numbers?
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/code_analysis.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index bb74d958..d776d81a 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -36,6 +36,11 @@ 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.
+
* [Static Source Code Analysis Tools for C](http://spinroot.com/static/)
* [[!wikipedia List_of_tools_for_static_code_analysis]]