Date: Thu, 19 Jul 2018 15:07:26 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 229888] devel/boost-libs: Fix undefined behavior in boost::filesystem::copy Message-ID: <bug-229888-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229888 Bug ID: 229888 Summary: devel/boost-libs: Fix undefined behavior in boost::filesystem::copy Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: office@FreeBSD.org Reporter: grembo@FreeBSD.org Assignee: office@FreeBSD.org Flags: maintainer-feedback?(office@FreeBSD.org) Attachment #195277 maintainer-approval? Flags: Flags: maintainer-feedback? Created attachment 195277 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D195277&action= =3Dedit Fix to boost::filesystem::copy There is a bug in boost::filesystem::copy that leads to undefined behavior = (and segfault on 11.2 + clang6 + stackprotector support). Example: int main() { boost::system::error_code ec; boost::filesystem::copy("/tmp/t.pdf", "/tmp/t2.pdf", ec); } This is caused by derefencing null pointers. There is already a pull request on github: https://github.com/boostorg/filesystem/pull/71 This patch pulls in this patch (tested) and fixes the issue. The same code worked on 10.3 with clang 3.9 (at least on an older ports tree), that's why this is a ticking time bomb for people upgrading to 11.2. --=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-229888-7788>