From owner-freebsd-threads@freebsd.org  Fri Jan 29 19:50:01 2016
Return-Path: <owner-freebsd-threads@freebsd.org>
Delivered-To: freebsd-threads@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC63EA72E59
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Fri, 29 Jan 2016 19:50:01 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C6DAF1033
 for <freebsd-threads@FreeBSD.org>; Fri, 29 Jan 2016 19:50:01 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0TJo1Zs081621
 for <freebsd-threads@FreeBSD.org>; Fri, 29 Jan 2016 19:50:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 204426] Processes terminating cannot access memory
Date: Fri, 29 Jan 2016 19:50:02 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 19:50:02 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426

--- 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 fau=
lts
you are seeing.  However, having proper core dumps is needed to debug the r=
oot
cause.

You can try backporting the changes I mentioned previously to your 10.2 ker=
nel
(you can get by with just the first two for testing) to see if we can get m=
ore
usaable core dumps to use in tracking down the root cause.  If you aren't u=
sed
to backporting changes I will try to do it in the next day or so (those fix=
es
should be in 10.3 anyway).  Once I've done the backport I can give you a pa=
tch
to apply to your 10.2 kernel.

--=20
You are receiving this mail because:
You are the assignee for the bug.=