public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/26830] New: gai_strerror(EAI_OVERFLOW) reports nothing useful
Date: Mon, 02 Nov 2020 12:51:10 +0000	[thread overview]
Message-ID: <bug-26830-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26830
           Summary: gai_strerror(EAI_OVERFLOW) reports nothing useful
           Product: glibc
           Version: 2.32
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: network
          Assignee: unassigned at sourceware dot org
          Reporter: jengelh at inai dot de
  Target Milestone: ---

Testcase:

#include <netdb.h>
#include <stdio.h>
#include <arpa/inet.h>
int main()
{
        struct sockaddr_in6 sa;
        inet_pton(AF_INET6, "2001:db8::1", &sa.sin6_addr);
        sa.sin6_family = AF_INET6;
        char host[2]; /* deliberately small */
        int ret = getnameinfo((struct sockaddr *)&sa, sizeof(sa), host,
                  sizeof(host), NULL, 0, NI_NUMERICHOST | NI_NUMERICSERV);
        if (ret != 0)
                printf("%s\n", gai_strerror(ret));
}

Observed:

"Unknown error"

Expected to see:

"Buffer too small" or something

Reason:

There is no error string defined for EAI_OVERFLOW (and possibly other codes).

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

             reply	other threads:[~2020-11-02 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 12:51 jengelh at inai dot de [this message]
2022-06-04 17:02 ` [Bug network/26830] " rob.ross at ymail 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-26830-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).