public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stlman at poczta dot fm" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2773] New: socklen_t type buffer lengths in inet_ntop() functions
Date: Wed, 14 Jun 2006 20:49:00 -0000	[thread overview]
Message-ID: <20060614204907.2773.stlman@poczta.fm> (raw)

Why are the size variables in libc/resolv/inet_ntop.c of type socklen_t instead
of size_t while in fact they have nothing to do with any socket structures?

I ask about this because I just had a proble when I read the header file and the
manual (*not* carefuly enough) and put *thoughtlessly* sizeof(struct sockaddr)
as fourth argument.  Of course it didn't work.

Indeed now for me this is only a matter of clarity but please answer.

-- 
           Summary: socklen_t type buffer lengths in inet_ntop() functions
           Product: glibc
           Version: 2.3.6
            Status: NEW
          Severity: minor
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: stlman at poczta dot fm
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2773

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2006-06-14 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 20:49 stlman at poczta dot fm [this message]
2006-06-14 21:04 ` [Bug libc/2773] " jakub at redhat dot com
2006-06-15  0:18 ` michael dot kerrisk at gmx dot net

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=20060614204907.2773.stlman@poczta.fm \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).