From fc08486fd989e724bd8df4a086d453612c4f2aba Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 24 Nov 2011 09:59:55 +0100 Subject: open_issues/code_analysis: Static code checker for port sequence numbers? --- open_issues/code_analysis.mdwn | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'open_issues') 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]] -- cgit v1.2.3