On Tue, May 18, 2010 at 10:32:13AM +0200, Bastian Blank wrote:
On Tue, May 18, 2010 at 03:47:58AM +0300, Faidon Liambotis wrote:
It seems that on consecutive runs of the test case[1] in question, it aborts
at different points each time and even succeeds in one in five runs or so.
Moreover, while the combined assert() condition fails, separate assert()
calls
for each of the condition succeed while their combination still fail(!)
Does tokyocabinet use multi-threading or some other means of
concurrency? For me this looks like race conditions. They may live in
the glibc, as there were some fixes in this area lately.
Thanks guys! Indeed tokyocabinet does use multi-threading.
$ find tokyocabinet-1.4.37/ -type f | xargs grep thread | wc -l
730
$ grep -c thread tokyocabinet-1.4.37/tcbmttest.c
60
Bastian, I don't see any related recent entries in the glibc changelog. If the
fixes are still pending, is there a bug we could denote as a blocker for
#40?
Cheers,
Serafeim
--
debtags-organised WNPP bugs: http://members.hellug.gr/serzan/wnpp
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100518211015.ga3...@mobee
