From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
To: Zhen Ren <zren-IBi9RG/b67k@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: "man 3 vsprintf" : simple bug in EXAMPLE section
Date: Fri, 27 Mar 2015 11:20:58 +0100 [thread overview]
Message-ID: <55152F0A.7090708@bfs.de> (raw)
In-Reply-To: <5515C2F9020000D400069A6F-8qcz4lDFMZvD8XXLLHKrIiOjQekVJEpY@public.gmane.org>
hi Zhen Ren,
i tried to create a more simple example. Do you think this is more
helpful for you ?
re,
wh
char *
make_message2 (const char *fmt, ...)
{
int n,size = 0;
char *p = NULL;
va_list ap;
/* figure our required size */
va_start (ap, fmt);
size = vsnprintf (p, size, fmt, ap);
va_end (ap);
if (size < 0)
return NULL;
/* leave room for \0 */
size++;
p = malloc (size);
if (p == NULL)
return NULL;
va_start (ap, fmt);
n = vsnprintf (p, size, fmt, ap);
va_end (ap);
return p;
}
Am 27.03.2015 10:52, schrieb Zhen Ren:
> Hi Michael,
>
> I'm so sorry for this negative report.
>
> Yeah, you're right. It'll fall through,loop again,do "vsprintf" and return if done.
>
> --
> Best regards,
> Eric, Ren
> HA team, SUSE
>
>
>>>>
>> Hello Zhen Ren,
>>
>> On 27 March 2015 at 06:27, Zhen Ren <zren-IBi9RG/b67k@public.gmane.org> wrote:
>>> Hi,
>>> There is simple bug in EXAMPLE section of "man 3 vsprintf".
>>>
>>> Function will return nothing if it steps into the last "else {}".
>>>
>>> ------------------ example code -----------------
>>> char *
>>> make_message(const char *fmt, ...)
>>> {
>>> int n;
>>> int size = 100; /* Guess we need no more than 100 bytes */
>>> char *p, *np;
>>> va_list ap;
>>> .
>>> .cut off
>>> .
>>> np = realloc(p, size);
>>> if (np == NULL) {
>>> free(p);
>>> return NULL;
>>> } else {
>>> p = np;
>>> + return p;
>>> }
>>> }
>>> }
>>
>> I have not looked too closely at the code, but the above report
>> appears incorrect to me. The function should NOT be returning at that
>> point. It should be falling through and then round the loop once more.
>> If I've missed something, could you elaborate a little more on the
>> problem, please?
>>
>> Cheers,
>>
>> Michael
>>
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-man" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-27 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 5:27 "man 3 vsprintf" : simple bug in EXAMPLE section Zhen Ren
[not found] ` <551584DE020000D400069A4C-8qcz4lDFMZvD8XXLLHKrIiOjQekVJEpY@public.gmane.org>
2015-03-27 6:06 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjY=YpuZ7ifA1HCN68jZZ_PgFRw4KYfKaXeViPAvs+m+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-27 9:52 ` Zhen Ren
[not found] ` <5515C2F9020000D400069A6F-8qcz4lDFMZvD8XXLLHKrIiOjQekVJEpY@public.gmane.org>
2015-03-27 10:20 ` walter harms [this message]
[not found] ` <55152F0A.7090708-fPG8STNUNVg@public.gmane.org>
2015-03-27 15:26 ` Zhen Ren
2015-04-11 7:30 ` Michael Kerrisk (man-pages)
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=55152F0A.7090708@bfs.de \
--to=wharms-fpg8stnunvg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zren-IBi9RG/b67k@public.gmane.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 NNTP newsgroup(s).