From: Reinhard Tartler <Reinhard.Tartler@informatik.uni-erlangen.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: vamos@i4.informatik.uni-erlangen.de, Julia Lawall <julia@diku.dk>
Subject: [ANNOUNCE] undertaker 1.0
Date: Thu, 27 Jan 2011 12:56:07 +0100 [thread overview]
Message-ID: <87y666tvag.fsf@faui44a.informatik.uni-erlangen.de> (raw)
The VAMOS team is pleased to announce the first release of undertaker 1.0.
The undertaker tool is a result of the VAMOS[1] research project.
Please visit our project site at:
http://vamos.informatik.uni-erlangen.de/trac/undertaker
What is undertaker?
-------------------
The undertaker is a tool for static code analysis for code with C
preprocessor directives, which can be used in various modes. The most
prominent one checks every single preprocessor block within the file
whether it can be selected or deselected, which in many cases is a great
asset for code maintenance.
Some preprocessor blocks are only seemingly conditional. In many cases,
it turns out that additional constraints from the project's configuration
model causes such conditional blocks to be in fact unconditionally selected
or unselected. We call such block "dead" and "undead" conditional blocks.
Undertaker provides tools to extract the configuration model from
the Linux configuration tooling Kconfig and to perform this check on whole
source trees.
We have already performed a check on the v2.6.38-rc1 tree and provide
easy access to the results via an online interface[2]. There is also a cpio
archive with the report files.
What undertaker is not?
-----------------------
It isn't an automatic patch generator. Because of peculiarities in the
Kconfig semantics, (ignored) coding guidelines and simply engineering
issues, the reports might contain false negatives. Note that our
philosophy is that we prefer false negatives over false positives, i.e.,
we prefer to miss reports than reports that are no issue at all.
What else can i do with undertaker?
-----------------------------------
You can extract boolean formulas (with or without model) for a given
line of sourcecode in a file or for a given symbol. There is also an
integration for emacs for interactive browsing of block and symbol
preconditions.
Additional uses are currently under development.
[1] http://www4.informatik.uni-erlangen.de/Research/VAMOS/
[2] http://www4.informatik.uni-erlangen.de/Research/VAMOS/linux-trees/
--
Reinhard Tartler Department of Computer Science IV
Martensstr 1, 91058 Erlangen Germany, University of Erlangen-Nuremberg
http://www4.informatik.uni-erlangen.de/~tartler
next reply other threads:[~2011-01-27 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 11:56 Reinhard Tartler [this message]
2011-01-28 20:41 ` Thomas Gleixner
2011-01-31 13:00 ` Christian Dietrich
2011-01-31 13:23 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y666tvag.fsf@faui44a.informatik.uni-erlangen.de \
--to=reinhard.tartler@informatik.uni-erlangen.de \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=vamos@i4.informatik.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®