From owner-freebsd-ports-bugs@FreeBSD.ORG  Thu May  7 16:16:44 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 2BCA0F14
 for <freebsd-ports-bugs@FreeBSD.org>; Thu,  7 May 2015 16:16:44 +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 15E971AD0
 for <freebsd-ports-bugs@FreeBSD.org>; Thu,  7 May 2015 16:16:44 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t47GGhWQ046835
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 7 May 2015 16:16:43 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: Thu, 07 May 2015 16:16:43 +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: luca.pizzamiglio@gmail.com
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: 
Message-ID: <bug-200001-13-1EaSKI5Ivr@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: Thu, 07 May 2015 16:16:44 -0000

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

--- Comment #3 from luca.pizzamiglio@gmail.com ---
Hi,

The big suspect here is the thread support and how the thread list is created
when the libthr.so is loaded. 

There was an issue with gdb78, (solved in the revision 365578) and I guess that
the fix is not able to handle the load of libthr.so when the process has
already more thread (attach or core dump load of multithread programs)

In other words, if you run the application inside gdb, libthr.so is processed
at the beginning, when only 1 thread is running and everything is fine.
gdb79 ./foo
tested, it works.

If you analyze the core dump or you dynamically attach gdb to a running
process, gdb has inconsistent information about threads.

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