Fixed bug in fm3tool that showed up if a user ran fm3tool with the wrong number of arguments. In such a case fm3tool attempts to display a usage statement but the statement is malformed, which causes a tcl stack dump.
Fixed bug in fm3tool that showed up if a user ran fm3tool with the
wrong number of arguments. In such a case fm3tool attempts to display a
usage statement but the statement is malformed, which causes a tcl
stack dump.

Users will rarely, if ever, call fm3tool directly. But if they do, and 
screw it up, we shouldn't give them a tcl stack trace.

bk: 3ecb1f65A8WITQTeMax6DaNJij5WdA
bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper,bitkeeper-scm/bitkeeper