goto-instrument's options require two file arguments and when not supplied, fails with a non-obvious help message #2861
Assignees
Comments
NlightNFotis
added a commit
to NlightNFotis/cbmc
that referenced
this issue
Feb 15, 2019
In the past, goto-instrument was failing with the default --help error message if it didn't get the correct number of positional arguments, making it unnecessarily hard to understand what was failing and why (since the help message is long and it also didn't have any particular signaling for what went wrong). This makes it so that it reports it as an invalid user input exception. Fixes diffblue#2861.
7 tasks
JohnDumbell
pushed a commit
to JohnDumbell/cbmc
that referenced
this issue
Feb 18, 2019
In the past, goto-instrument was failing with the default --help error message if it didn't get the correct number of positional arguments, making it unnecessarily hard to understand what was failing and why (since the help message is long and it also didn't have any particular signaling for what went wrong). This makes it so that it reports it as an invalid user input exception. Fixes diffblue#2861.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
goto-instrument, as mentioned in #2793, needs two file arguments passed for most of the command line arguments it supports (given it's just transformations that are read from one goto-binary, applied, and then written to another goto-binary). When it's not given two file arguments for these options, it fails with its generic--helpmessage, failing to make obvious what has gone wrong.The text was updated successfully, but these errors were encountered: