This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/14500] socket data is truncated for data length ~ 4-5 K


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]