From owner-freebsd-ports-bugs@FreeBSD.ORG  Mon May 11 20:20:49 2015
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BC4E9D00
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 11 May 2015 20:20:49 +0000 (UTC)
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 A5F21172F
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 11 May 2015 20:20:49 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4BKKnQ2025382
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 11 May 2015 20:20:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 200001] devel/gdb: gdb 7.9 crashes on certain core files
Date: Mon, 11 May 2015 20:20:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-200001-13-cRXvL1e1sp@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200001-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-200001-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 May 2015 20:20:49 -0000

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

--- Comment #6 from John Baldwin <jhb@FreeBSD.org> ---
Created attachment 156667
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156667&action=edit
clear_thread_list.patch

This is the workaround I've been testing.  It does fix this, but it's not clear
to me what the most correct fix for this is.  Other libthread_db targets in gdb
for Solaris and Linux just avoid attaching to core dumps entirely.  This patch
makes the FreeBSD thread target throw away the threads enumerated by the
default core dump target and re-enumerate them using the FreeBSD target
directly.

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