[gstreamer-bugs] [Bug 602312] multiudpsink Windows 7 64 bits

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=602312
  GStreamer | gst-plugins-good | unspecified

Richard Spiers <richard.spiers> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richard.spiers at gmail.com

--- Comment #2 from Richard Spiers <richard.spiers at gmail.com> 2010-03-09 21:46:04 UTC ---
Hi all

I have been commenting on bug 604870
(https://bugzilla.gnome.org/show_bug.cgi?id=604870) as I encountered this
problem while looking at that bug.

Michael, as you mentioned above WSAGetLastError is missing in
gstmultiudpsink.c.

I added it and got two error codes while poking around

WSAEFAULT (10014)

"Bad address.
The system detected an invalid pointer address in attempting to use a pointer
argument of a call. This error occurs if an application passes an invalid
pointer value, or if the length of the buffer is too small. For instance, if
the length of an argument, which is a sockaddr structure, is smaller than the
sizeof(sockaddr)."

WSAEMSGSIZE (10040)

"Message too long.
A message sent on a datagram socket was larger than the internal message buffer
or some other network limit, or the buffer used to receive a datagram was
smaller than the datagram itself."

Re the size message, could this be related to bug 610364
(https://bugzilla.gnome.org/show_bug.cgi?id=610364) ?

I am more than happy to test out things / change some code, but would need a
bit of guidance here - I am running on a windows 7 pc, and have tried multiple
different pipelines etc - all of them lead to no network traffic appearing
because of the break in the code above when an error is detected.

Any advice / suggestions would be most welcome, I really want to get this
sorted :)

Thanks

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.