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 57771 - Take advantage of exposed GString allocation API in GIOChannel implementation
Take advantage of exposed GString allocation API in GIOChannel implementation
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
1.3.x
Other All
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2001-07-19 19:01 UTC by Ron Steinke
Modified: 2011-02-18 15:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ron Steinke 2001-07-19 19:01:28 UTC 






Comment 1


Owen Taylor





          2001-07-23 19:04:02 UTC
        



Is this really fixed? I don't see any changes in this part
of the code.






Comment 2


Ron Steinke





          2001-08-16 23:36:19 UTC
        



Fixed in CVS: copying to write_buf and encoded_read_buf
pays attention to the actual length of memory allocated.
This is intentionally not done for read_buf, so that
file accesses always try to pull in buf_size bytes
worth of data