Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 May 2016 16:01:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-threads@FreeBSD.org
Subject:   [Bug 209194] Seg fault with pthread_cond_signal() and pthread_cond_broadcast()
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209194-16-2FOIhu2gxP>