Goto Fail, Heartbleed, and Unit Testing Culture
martinfowler.com
martinfowler.com
Simplest plan is probably to simulate the binary and throw a combination of valid and fuzzed inputs to get an idea of which paths are taken; then you -might- be able to figure out what combination of inputs and events could lead to the bits you've not hit already.
Isn't that at the compiler level rather than binary though? It's definitely a lot easier when you're compiling, yes!