Date: Sat, 15 Jul 2017 07:47:09 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 217635] lang/beignet: crash in get_program_global_data() after 1.3.0 update Message-ID: <bug-217635-7141-WtgVaK4LWw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217635-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-217635-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=3D217635 --- Comment #18 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Kubilay Kocak from comment #14) > Approved by: portmgr (maintainer timeout, 4+ months) Actually, the patch qualified for portmgr blanket as soon as it landed upstream. The stalemate is caused by disagreement about QA. For background = see https://lists.freebsd.org/pipermail/svn-ports-head/2017-April/144802.html (In reply to Matthew Rezny from comment #17) > This patch is not applicable as-is Ignoring trivial PORTREVISION conflict the other hunk still applies. And patch-level updates rarely change semantics to require re-evaluation of assumptions. > since the port was updated some time ago, Only 1.4.0 (unreleased atm) has the fix. > nor has it been made clear whether the workaround is still needed after t= hat update. Notice comment 11 or https://lists.freebsd.org/pipermail/freebsd-questions/2017-July/277987.html confirm the crash disappeared by either downgrading to 1.2.0 or applying t= he patch. comment 4 was invalidated by comment 9 but both are so context-heavy, so le= t's ignore those. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217635-7141-WtgVaK4LWw>