After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 306912 - gamin_write_byte/gam_client_conn_write don't loop over write()
gamin_write_byte/gam_client_conn_write don't loop over write()
Status: RESOLVED FIXED
Product: gamin
Classification: Other
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: Gamin Maintainer(s)
Gamin Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-06-08 16:03 UTC by Neal H. Walfield
Modified: 2005-06-08 17:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch (2.79 KB, patch)
2005-06-08 16:03 UTC, Neal H. Walfield 		none Details | Review

Description Neal H. Walfield 2005-06-08 16:03:11 UTC 
Please describe the problem:
Quoting from the glibc manual:

     The `write' function writes up to SIZE bytes from BUFFER to the
     file with descriptor FILEDES.  The data in BUFFER is not
     necessarily a character string and a null character is output like
     any other character.

     The return value is the number of bytes actually written.  This
     may be SIZE, but can always be smaller.  Your program should
     always call `write' in a loop, iterating until all the data is
     written.

gamin_write_byte and gam_client_conn_write don't do this but should.


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Neal H. Walfield 2005-06-08 16:03:36 UTC 
Created attachment 47455 [details] [review]
patch
Comment 2 Daniel Veillard 2005-06-08 17:22:26 UTC 
 Yes you're right, it applies fine, and the regression tests
still passes okay, so applied and commited,

  thanks !

Daniel