multisocketsink: fix "client-removed" signal on 64-bit platforms and with bindings upstream/1.6
authorCsaba Toth <tocsanti@gmail.com>
Mon, 26 Oct 2015 20:32:41 +0000 (21:32 +0100)
committerTim-Philipp Müller <tim@centricular.com>
Sat, 31 Oct 2015 11:50:45 +0000 (11:50 +0000)
The client-removed signal used G_INT_TYPE instead of G_SOCKET_TYPE
in its definition leading to problems on platforms where the size
of a pointer is larger than the size of an integer, It would also
not work at all with dynamic language bindings.

https://bugzilla.gnome.org/show_bug.cgi?id=757155

gst/tcp/gstmultisocketsink.c

index d8e587b..cf5a4a5 100644 (file)
@@ -326,7 +326,7 @@ gst_multi_socket_sink_class_init (GstMultiSocketSinkClass * klass)
   gst_multi_socket_sink_signals[SIGNAL_CLIENT_REMOVED] =
       g_signal_new ("client-removed", G_TYPE_FROM_CLASS (klass),
       G_SIGNAL_RUN_LAST, 0, NULL, NULL, g_cclosure_marshal_generic,
-      G_TYPE_NONE, 2, G_TYPE_INT, GST_TYPE_CLIENT_STATUS);
+      G_TYPE_NONE, 2, G_TYPE_SOCKET, GST_TYPE_CLIENT_STATUS);
   /**
    * GstMultiSocketSink::client-socket-removed:
    * @gstmultisocketsink: the multisocketsink element that emitted this signal