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 591378 - Use MSG_NOSIGNAL in GSocket if it's available
Use MSG_NOSIGNAL in GSocket if it's available
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-08-10 21:35 UTC by Dan Winship
Modified: 2009-08-19 16:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use MSG_NOSIGNAL in GSocket if it's available (1.77 KB, patch)
2009-08-10 21:35 UTC, Dan Winship 		none Details | Review

Description Dan Winship 2009-08-10 21:35:17 UTC 
Even though we ignore SIGPIPE, gdb will still stop when the process
receives one, which sometimes confuses people into thinking the app
has crashed (eg, bug 578984, bug 590420), and is annoying anyway. So
use MSG_NOSIGNAL if it's there.
Comment 1 Dan Winship 2009-08-10 21:35:20 UTC 
Created attachment 140381 [details] [review]
Use MSG_NOSIGNAL in GSocket if it's available
Comment 2 Dan Winship 2009-08-19 16:13:06 UTC 
committed