Date: Fri, 29 Jan 2016 19:50:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-M1g7NO1nDN@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426 --- Comment #19 from John Baldwin <jhb@FreeBSD.org> --- Oh, I should be clear that the revisions I mentioned only address the issue of core dumps being corrupt, it does not address the root cause of the seg faults you are seeing. However, having proper core dumps is needed to debug the root cause. You can try backporting the changes I mentioned previously to your 10.2 kernel (you can get by with just the first two for testing) to see if we can get more usaable core dumps to use in tracking down the root cause. If you aren't used to backporting changes I will try to do it in the next day or so (those fixes should be in 10.3 anyway). Once I've done the backport I can give you a patch to apply to your 10.2 kernel. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-M1g7NO1nDN>