Truepath Analysis

Ever been faced with that glassy-eyed expression, the look of unthinking, unwholesome fear when some long, incomprehensible word escapes your geeky mouth and upsets the maiden aunts around the once-a-year, wear-your-best-tie, try-not-to-die-before-the-cake’s-all-gone tea table? OK, so this paper won’t help you in that situation whatsoever, but if you replace your maiden aunts with a bunch of your best geek friends, and replace the tea with a sturdy helping of Dew, knowing how a real whole program analysis solution works might just conceivably come in handy. Some day. “Dude, I was totally stoked when I read this thing, trust me it’s ahh-some.” Maybe.

Anyway, in the best traditions of self-serving corporate PR blogs everywhere, I give you… drum roll please… Whole Program Analysis, the Klocwork Way.

Enjoy.

Related posts:

1. Build Analysis and Source code analysis must work together
2. Dealing with a different type of backlog…your bug backlog
3. Embedded Systems Engineering – German 2009 Edition

Tags: source code analysis, Truepath

This entry was posted on Tuesday, August 11th, 2009 at 10:52 and is filed under General Coding, General Industry, Nasty Bugs, Software Quality, Software Security, Software Testing. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.