public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/14500] socket data is truncated for data length ~ 4-5 K
Date: Tue, 15 Jan 2013 11:14:00 -0000	[thread overview]
Message-ID: <bug-14500-131-RAruJqFbvD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14500-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #4 from Florian Weimer <fweimer at redhat dot com> 2013-01-15 11:14:21 UTC ---
(In reply to comment #0)
>     //send a request
>     nbytes = send(s, msg, n, 0); //some request
>     if (nbytes < 0) {perror("send");return 1;}

You should check the value of nbytes.

Closing a streaming socket which still has unread data will abort the
connection.  Connection aborts are delivered out of order.  Perhaps this is
what you're seeing.  (Stevens' UNIX Network Programming covers this corner case
quite well.)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-01-15 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14500-131@http.sourceware.org/bugzilla/>
2012-08-20 22:57 ` a.herefishyfishies at yahoo dot com
2012-08-20 22:59 ` a.herefishyfishies at yahoo dot com
2013-01-15 10:46 ` schwab@linux-m68k.org
2013-01-15 11:14 ` fweimer at redhat dot com [this message]
2014-06-17  5:57 ` fweimer 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-14500-131-RAruJqFbvD@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).