This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/19192] __old_sem_wait never terminates
- From: "jurobystricky at hotmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 02 Nov 2015 17:34:27 +0000
- Subject: [Bug nptl/19192] __old_sem_wait never terminates
- Auto-submitted: auto-generated
- References: <bug-19192-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19192
--- Comment #2 from Juro Bystricky <jurobystricky at hotmail dot com> ---
(In reply to Florian Weimer from comment #1)
> Does the hang happen on every call to __old_sem_wait?
It is hard to say. In my case the semaphore is initialized via
"new_sem_init" but then the wait for semaphore is via "old_sem_wait".
In this case there will be always problems, as the two calls assume different
structure for sem_t. Prior to glibc 2.21 this would work as well,
as the two different structures agreed on interpretation of the field "value".
Normally, I would expect no problems with combination
old_sem_init/old_sem_wait.
I should clarify that I ran into this problem using Python 2.7/multiprocessing.
--
You are receiving this mail because:
You are on the CC list for the bug.