Date: Sun, 09 Jul 2017 06:09:50 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 220565] net/libvncserver (was x11-servers/xorg-server): incompatible ABI change crashes VirtualBox Message-ID: <bug-220565-7141-ovYP4rpgEz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220565-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-220565-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220565 Martin Birgmeier <la5lbtyi@aon.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|x11-servers/xorg-server: |net/libvncserver (was |crashes VirtualBox, |x11-servers/xorg-server): |starting with r445076, also |incompatible ABI change |with r445323 |crashes VirtualBox --- Comment #7 from Martin Birgmeier <la5lbtyi@aon.at> --- Yes, VNC is enabled, and rolling back to libvncserver-0.9.11 fixes the prob= lem. It's not very clever to hide an ABI-breaking change in a bugfix-only update= - normally this warrants a bump of the library major version number. I don't have WITHOUT_NO_STRICT_ALIASING enabled, so I won't pursue the sdl route any further. Do you think that recompiling the ports dependent on libvncserver fixes the issue? I am going to edit the PR subject so that the port maintainer is notified. Thank you for your help. -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220565-7141-ovYP4rpgEz>