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?
Yes it does heavily in the test-suite. > For me this looks like race conditions. I agree with this. > They may live in the glibc, as there were some fixes in this area > lately. The fact that no other architecture has ever shown the same failures indeed points towards multithreading issues on 390 in the kernel or glibc. -- ·O· Pierre Habouzit ··O madco...@debian.org OOO http://www.madism.org -- 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/20100519123439.gb20...@madism.org
