[MacPorts] #34519: LibVNCServer 0.9.9 segfaults

[MacPorts]

#34519: LibVNCServer 0.9.9 segfaults
-------------------------------+--------------------------------------------
 Reporter:  mackyle@…          |       Owner:  ryandesign@…           
     Type:  defect             |      Status:  assigned               
 Priority:  Normal             |   Milestone:                         
Component:  ports              |     Version:  2.1.1                  
 Keywords:  haspatch           |        Port:  LibVNCServer           
-------------------------------+--------------------------------------------
Changes (by ryandesign@…):

  * owner:  macports-tickets@… => ryandesign@…
  * keywords:  => haspatch
  * status:  new => assigned
 * cc: mackyle@… (removed)


Old description:

> As of
> [http://svn.macports.org/repository/macports/trunk/dports/devel/LibVNCServer/Portfile]@92750,
> the 0.9.9 release of LibVNCServer is being used which includes new IPv6
> support.
>
> Now LibVNCServer will attempt to bind both an IPv4 and IPv6 socket for
> listening.  Unfortunately, if one of those fails and the other succeeds
> for some reason (maybe the IPv6 port is in use, but the IPv4 port is
> not), the server will segfault as soon as a connection arrives.
>
> This little problem is known to affect the VirtualBox port.
>
> Adding the following to the LibVNCServer Portfile:
>
> {{{
> # Don't segfault when listenSock/listen6Sock == -1
> patchfiles                  patch-libvncserver-0.9.9-no-segfault.diff
> }}}
>
> along with the attached files/patch-libvncserver-0.9.9-no-segfault.diff
> patch file fixes the problem.
>
> The patch has already been submitted upstream (see
> [http://sourceforge.net/tracker/?func=detail&atid=405860&aid=3527807&group_id=32584]),
> but until that appears in a released LibVNCServer version which is then
> picked up by MacPorts, any ports that use LibVNCServer to create a VNC
> server are liable to segfault.

New description:

 As of r92750, the 0.9.9 release of LibVNCServer is being used which
 includes new IPv6 support.

 Now LibVNCServer will attempt to bind both an IPv4 and IPv6 socket for
 listening.  Unfortunately, if one of those fails and the other succeeds
 for some reason (maybe the IPv6 port is in use, but the IPv4 port is not),
 the server will segfault as soon as a connection arrives.

 This little problem is known to affect the VirtualBox port.

 Adding the following to the LibVNCServer Portfile:

 {{{
 # Don't segfault when listenSock/listen6Sock == -1
 patchfiles                  patch-libvncserver-0.9.9-no-segfault.diff
 }}}

 along with the attached files/patch-libvncserver-0.9.9-no-segfault.diff
 patch file fixes the problem.

 The patch has already been submitted upstream (see
 [http://sourceforge.net/tracker/?func=detail&atid=405860&aid=3527807&group_id=32584]),
 but until that appears in a released LibVNCServer version which is then
 picked up by MacPorts, any ports that use LibVNCServer to create a VNC
 server are liable to segfault.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/34519#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS