With the pervasive connectivity of embedded designs, a new set of software debug challenges has emerged that are pushing traditional tools such as static analyzers to their limits – and beyond – to meet to meet the requirements of reliable code development.

Code problems in distributed systems such as wireless sensor networks cannot be easily located with a debugger. The author explains how to find them by capturing the call stack in real time and using it to stack dump at the point of failure.

An extension of the Julia static analyzer for Java language code to perform formally correct analyses of Android programs consisting of a mix of C, XML and Java.

A two-step WSN-specific model checker for software verification, first translating source code is first translated into model specific form and then verified against user-provided properties.

A two pass static analysis based system for effective taint analysis of framework-based web applications which use code from several different external sources.

How a static analyzer, called SCANDAL, can be used to detect privacy leaks in Android applications.

The majority of the news over the past few weeks about the Heartbleed bug in OpenSSL has focused on consumer usernames and passwords security. It’s also worth understanding how Heartbleed affects and informs us about security in embedded designs.

Using some open source Internet software, David Kleidermacher of GHS illustrates the benefits of static code analysis and how to use such techniques to test and debug your embedded software

A case study in how static analysis can be used to find and eliminate coding errors in three popular safety critical open source applications – Apache, OpenSSL and sendmail.

The effective use of static source code analysis to deal with the increasing complexity of software and the need to make sure code is reliable and bug free without seriously delaying product development.

When used early in software development, static analysis tools can reduce bugs in your code by allowing coverage of the execution paths through a very large code base in a fully automated way.

A user study involving 20 software developers who have an average of about 10 years of experience with using static analysis tools to find bugs.