*/
/**
- * SECTION: gsocketcontrolmessage
+ * SECTION:gsocketcontrolmessage
* @title: GSocketControlMessage
* @short_description: A GSocket control message
+ * @include: gio/gio.h
* @see_also: #GSocket.
*
* A #GSocketControlMessage is a special-purpose utility message that
*
* The message can represent some sort of special instruction to or
* information from the socket or can represent a special kind of
- * transfer to the peer (for example, sending a file description over
+ * transfer to the peer (for example, sending a file descriptor over
* a UNIX socket).
*
* These messages are sent with g_socket_send_message() and received
GType *message_types;
guint n_message_types;
int i;
-#ifndef G_OS_WIN32
- volatile GType a_type;
-#endif
/* Ensure we know about the built in types */
#ifndef G_OS_WIN32
- a_type = g_unix_credentials_message_get_type ();
- a_type = g_unix_fd_message_get_type ();
+ g_type_ensure (G_TYPE_UNIX_CREDENTIALS_MESSAGE);
+ g_type_ensure (G_TYPE_UNIX_FD_MESSAGE);
#endif
message_types = g_type_children (G_TYPE_SOCKET_CONTROL_MESSAGE, &n_message_types);
g_free (message_types);
- if (message == NULL)
- g_warning ("unknown control message type %d:%d", level, type);
+ /* It's not a bug if we can't deserialize the control message - for
+ * example, the control message may be be discarded if it is deemed
+ * empty, see e.g.
+ *
+ * http://git.gnome.org/browse/glib/commit/?id=ec91ed00f14c70cca9749347b8ebc19d72d9885b
+ *
+ * Therefore, it's not appropriate to print a warning about not
+ * being able to deserialize the message.
+ */
return message;
}