Matt,
On Tue, Mar 17, 2015 at 10:55:30AM +0000, Matt Fleming wrote:
> > +void fw_cfg_option_add(QemuOpts *opts)
> > +{
> > + const char *name = qemu_opt_get(opts, "name");
> > + const char *file = qemu_opt_get(opts, "file");
> > +
> > + if (name == NULL || *name == '\0' || file == NULL || *file == '\0') {
> > + error_report("invalid argument value");
> > + exit(1);
> > + }
>
> Just because I know I'm going to get this wrong when I start using it,
> can this error message mention that the fw_cfg argument is invalid,
> rather than being ambiguous?
With a command line containing e.g. "-fw_cfg file=,name=" to trigger
that error, the full error message ends up reading like this:
qemu-system-x86_64: -fw_cfg file=,name=: invalid argument value
So I figured anything more specific would end up repeating "fw_cfg"
too many times on the same line of output... :)
What do you think ?
Thanks,
--Gabriel
