From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] test specific command line options
Date: Thu, 28 Jul 2016 08:23:11 -0400 (EDT) [thread overview]
Message-ID: <1842886039.9326772.1469708591634.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160728081249.GA4664@bogon>
----- Original Message -----
> From: "Han Pingtian" <hanpt@linux.vnet.ibm.com>
> To: ltp@lists.linux.it
> Sent: Thursday, 28 July, 2016 10:12:49 AM
> Subject: [LTP] test specific command line options
>
> Hi,
>
> From the doc I read:
>
> ... The 'arg' is where 'optarg' is stored upon match. If option has no
> parameter it's set to non-'NULL' value if option was present.
>
> But looks like if a option was present which has no parameter, the 'arg'
> will set to NULL?
You're right, that looks like a BUG. If you don't provide colon,
then "arg" stays NULL, but doc say it should be non-NULL:
diff --git a/lib/tst_test.c b/lib/tst_test.c
index 4f417ea345e7..0b99bedd8d81 100644
--- a/lib/tst_test.c
+++ b/lib/tst_test.c
@@ -384,6 +384,7 @@ static void parse_topt(unsigned int topts_len, int opt, char *optarg)
{
unsigned int i;
struct tst_option *toptions = tst_test->options;
+ static char *match = "";
for (i = 0; i < topts_len; i++) {
if (toptions[i].optstr[0] == opt)
@@ -393,7 +394,10 @@ static void parse_topt(unsigned int topts_len, int opt, char *optarg)
if (i >= topts_len)
tst_brk(TBROK, "Invalid option '%c' (should not happen)", opt);
- *(toptions[i].arg) = optarg;
+ if (optarg)
+ *(toptions[i].arg) = optarg;
+ else
+ *(toptions[i].arg) = match;
}
/* see self_exec.c */
Regards,
Jan
>
> Thanks in advance.
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
next prev parent reply other threads:[~2016-07-28 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 8:12 [LTP] test specific command line options Han Pingtian
2016-07-28 12:23 ` Jan Stancek [this message]
2016-08-01 9:23 ` Cyril Hrubis
2016-08-01 9:50 ` Jan Stancek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1842886039.9326772.1469708591634.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox