Comment 4 for bug 941103

Sorry, but from the above output and looking at the source code touched in r12972, it doesn't *look* like anything relevant was fixed. (Feel free to re-close this bug with an appropriate summary if the bug is actually fixed, but please test it first.)

~suv, notice that in your cut-and-pasted error output, you're not triggering the assertion codepath. The error messages you're getting are because you've given *input* filenames which don't exist. The reported assertion-failure happens when the *output* file cannot be created. Create your input files first, *then* try the supplied command lines.

(BTW, it's also weird that a single missing input file gave you *three* error messages on stderr. Surely there's some UX work to be done in that area.)