From: Girish Joshi <girish946@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] argp: argp.doc prints incorrectly when it starts with "\v" [BZ #19038]
Date: Mon, 6 May 2019 09:38:06 -0400 [thread overview]
Message-ID: <CALkY8p9c7BtRoivZ0wpBP-XDoyNibpQ4Ri4Deyr1aFnafbmhLg@mail.gmail.com> (raw)
In-Reply-To: <871s1bep2u.fsf@oldenburg2.str.redhat.com>
Hi Florian,
> I assume this bug user-visible, so it should have a bug in Bugzilla
> <https://sourceware.org/bugzilla/>. Would you please file one?
>
Here[1] is a Bugzilla entry for this.
> Could you write a test case for this? Or at least post how to reproduce
> the issue in a minimal program?
>
It can be reproduced with following code.
#include<stdlib.h>
#include<argp.h>
static char doc[] = "\vthis is post_doc";
static struct argp argp = {NULL, NULL, NULL, doc};
int main(int argc, char *args[]){
argp_parse(&argp, argc, args, 0, 0, NULL);
}
the output of the above code looks like:
this is post_doc
-?, --help Give this help list
--usage Give a short usage message
this is post_doc
In this case the doc is being printed two times.
As mentioned in the comment by Kenny Stauffer on Bugzilla the first
occurrence of `this is post_doc` is erroneous.
If we change the doc[] in the above code to something else like
static char doc[] = "this is pre_doc\vthis is post_doc";
We get the output like:
this is pre_doc
-?, --help Give this help list
--usage Give a short usage message
this is post_doc
[1]: https://sourceware.org/bugzilla/show_bug.cgi?id=19038
next prev parent reply other threads:[~2019-05-06 13:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 8:55 [PATCH] argp: argp.doc prints incorrectly when it starts with "\v" [BZ #19038] Girish Joshi
2019-05-06 12:37 ` Florian Weimer
2019-05-06 13:38 ` Girish Joshi [this message]
2019-05-30 8:14 ` Girish Joshi
2019-05-30 12:52 ` Adhemerval Zanella
2019-07-05 9:01 ` Girish Joshi
2019-07-05 10:34 ` Girish Joshi
2019-07-25 15:33 ` Joseph Myers
2019-11-25 18:08 ` Girish Joshi
2019-11-30 14:47 ` Girish Joshi
2019-11-30 15:05 ` Carlos O'Donell
2020-01-07 17:55 ` Girish Joshi
2020-01-20 17:21 ` Girish Joshi
2020-01-24 2:38 ` Carlos O'Donell
2020-02-11 18:40 ` Girish Joshi
2020-02-20 7:09 ` Girish Joshi
-- strict thread matches above, loose matches on Subject: below --
2020-03-03 18:13 Girish Joshi
2020-03-19 19:38 ` Girish Joshi via Libc-alpha
2020-03-21 2:03 ` DJ Delorie via Libc-alpha
2020-03-25 17:55 ` Girish Joshi via Libc-alpha
2020-05-07 19:53 ` Girish Joshi via Libc-alpha
2020-05-23 10:10 ` Girish Joshi via Libc-alpha
2020-06-14 15:50 ` Girish Joshi via Libc-alpha
2020-06-15 8:56 ` Florian Weimer via Libc-alpha
2020-06-15 9:51 ` Girish Joshi via Libc-alpha
2020-06-15 14:38 ` Zack Weinberg
2021-02-18 21:13 ` Girish Joshi via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkY8p9c7BtRoivZ0wpBP-XDoyNibpQ4Ri4Deyr1aFnafbmhLg@mail.gmail.com \
--to=girish946@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).