bsondump prints "0 objects found" in cases where it shouldn't be getting to the point where it can try to read objects.
For instance, when given an invalid --type:
2014-12-05T13:31:34.783-0500 shell: started program bsondump --type=fake jstests/bsondump/testdata/sample.bson sh24515| 2014-12-05T13:31:34.789-0500 0 objects found sh24515| 2014-12-05T13:31:34.789-0500 Unsupported output type 'fake'. Must be either 'debug' or 'json'
Or a non-existent file:
2014-12-05T13:32:13.080-0500 0 objects found 2014-12-05T13:32:13.080-0500 Couldn't open BSON file: open adsf: no such file or directory
Ideally, we wouldnt print object counts unless we were able to read and attempt to parse a file. The only case that generates "0 objects found" should be when the tool is given an empty .bson file