Date: Fri, 29 Jan 2016 18:44:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-Zjevnt26bd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/> References: <bug-204426-16@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=3D204426 --- Comment #16 from John Baldwin <jhb@FreeBSD.org> --- Hmm, the EFAULT error (14) is quite odd. I wonder if you tripped over the = bug that is fixed in HEAD by r287442, r287537, and r288944. That bug was present in 10.1 though (and 10.0), not unique to 10.2. Howeve= r, a corrupted core dump is why you can't do a full backtrace. :( --=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-204426-16-Zjevnt26bd>