[gstreamer-bugs] [Bug 557610] New: udpsrc fails to bind() on Mac OS X (IPv4 vs. IPv6 problem)

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=557610

  GStreamer | gst-plugins-good | Ver: 0.10.10
           Summary: udpsrc fails to bind() on Mac OS X (IPv4 vs. IPv6
                    problem)
           Product: GStreamer
           Version: 0.10.10
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: anders at odlund.se
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
The udpsrc component (used by the rtsp source componet) fails with the
following error on Mac OS X (10.5)

udpsrc gstudpsrc.c:763:gst_udpsrc_start:<udpsrc0> allocating socket for
0.0.0.0:0
udpsrc gstudpsrc.c:780:gst_udpsrc_start:<udpsrc0> binding on port 0
udpsrc gstudpsrc.c:887:gst_udpsrc_start:<udpsrc0> error: bind failed -1:
Invalid argument (22)

The error is due to the address_len being the wrong size: sizeof(src->myaddr)
instead of sizeof(struct sockaddr_in), I'd guess this is due to differences
between IPv4 and IPv6.

I'm pretty sure this is related to what's described in #534243

Steps to reproduce:
1. Use the rtspsrc filter to access a UDP rtsp url on Mac OS X 10.5


Actual results:
The pipeline fails to start

Expected results:
The pipeline would start

Does this happen every time?
Yes

Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=557610.