From owner-freebsd-threads@freebsd.org  Mon May  2 16:01:20 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 31580AEE32F
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Mon,  2 May 2016 16:01:20 +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 1AF9818DE
 for <freebsd-threads@FreeBSD.org>; Mon,  2 May 2016 16:01:20 +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 u42G1Jqx036341
 for <freebsd-threads@FreeBSD.org>; Mon, 2 May 2016 16:01:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 209194] Seg fault with pthread_cond_signal() and
 pthread_cond_broadcast()
Date: Mon, 02 May 2016 16:01:20 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: michael.cress@cress.us
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-209194-16-2FOIhu2gxP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209194-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-209194-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.22
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: Mon, 02 May 2016 16:01:20 -0000

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

--- Comment #2 from Michael Cress <michael.cress@cress.us> ---
Is it possible to get a version of this library with the debugging informat=
ion
compiled in? I agree that the most likely explanation is a bug in my code as
the unit tests for that section of code execute correctly. However, examini=
ng
the data structures using GDB between succeeding and failing calls, I have
verified that the cond var and the lock memory addresses are not being
modified. Visibility and access to the lock and cond vars does not escape t=
he
.c file so I can't see where overwriting or corruption of the lock and cond
vars could happen.

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