readelf. We modified it's source code too to output and xml file based on the DWARF2 data in the elf file
Prefast. Useful hints on what kind of flaws we can determine
libelf. this is used to locate the dwarf .debug_* sections in the elf binary
dwarf2xml. These guys gave us the ideea to modify readelf to output xml data. They also have an interesting paper argumenting the bennefits and downsides of static checking and build some little applications (get a function call graph and cross-referencers).
libdwarf. Trust me, you don't really want to read dwarf2 information directly just through libelf. dwarf2 is designed to use very little space to represent it's knowledge so you'll have loooots of bits and bitfields and fuuun. NOT
Windows IPC Fuzzing Tools | Information Security Partners, LLC: "This is a collection of tools used to attack applications that use Windows Interprocess Communication mechanisms. This package includes tools to intercept and fuzz named pipes, as well as a shared memory section fuzzer."