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 748308 - giochannel: not always able to distinguish connection close from generic error
giochannel: not always able to distinguish connection close from generic error
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: general
2.44.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-04-22 15:26 UTC by Ognyan Tonchev (redstar_)
Modified: 2018-05-24 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ognyan Tonchev (redstar_) 2015-04-22 15:26:16 UTC 
g_io_channel_read_line() returns G_IO_CHANNEL_ERROR_FAILED when other end closes connection and errno is ECONNRESET.
How about changing the API so that it returns EOF in this case too or at least Error Code/Error Domain are properly set, for example to G_IO_CHANNEL_ERROR_CONNRESET.

Currently G_IO_CHANNEL_ERROR_CONNRESET is not present unlike G_IO_CHANNEL_ERROR_PIPE for example.

Would you accept any change in this respect?
Comment 1 GNOME Infrastructure Team 2018-05-24 17:47:42 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1029.