public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mlichvar at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug argparse/28081] New: getopt_long doesn't return error on ambigouos option
Date: Mon, 12 Jul 2021 15:55:24 +0000	[thread overview]
Message-ID: <bug-28081-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28081

            Bug ID: 28081
           Summary: getopt_long doesn't return error on ambigouos option
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: argparse
          Assignee: unassigned at sourceware dot org
          Reporter: mlichvar at redhat dot com
  Target Milestone: ---

An option which partially matches multiple getopt long options doesn't produce
an error.

Reproducer:
#include <stdio.h>
#include <getopt.h>

int main(void) {
        const char *argv[] = {"a", "--f", "b", NULL };
        int index, c;

        static struct option long_options[] = {
                {"foobar", required_argument, 0, 0},
                {"foobaz", required_argument, 0, 0},
                {0, 0, 0, 0}
        };

        c = getopt_long(3, (char **)argv, "", long_options, &index);

        printf("c=%d index=%d\n", c, index);
}

Actual result:
c=0 index=0

Expected result:
option '--f' is ambiguous; possibilities: '--foobar' '--foobaz'
c=63 index=0

More information:
It seems this doesn't happen when the two options are different in the
required_argument vs no_argument setting.

Observed on Fedora 34 using glibc-2.33-16.fc34.x86_64.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-07-12 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 15:55 mlichvar at redhat dot com [this message]
2021-07-12 16:01 ` [Bug argparse/28081] getopt_long doesn't return error on ambiguous option mlichvar at redhat dot com
2021-07-12 16:12 ` schwab@linux-m68k.org
2021-07-12 16:15 ` mlichvar at redhat dot com
2021-07-12 17:56 ` schwab@linux-m68k.org
2021-07-13  7:34 ` mlichvar at redhat dot com
2021-07-19  7:48 ` mlichvar at redhat dot com

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=bug-28081-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).