Comment #4 on issue 3604 by [email protected]: Tests calling
sem_destroy() on semaphore with waiters
https://code.google.com/p/v8/issues/detail?id=3604
Hm, it seems that this problem is still not completely fixed.
I still have many tests where sem_destroy() fails with EBUSY.
I've added perror() printouts when these fail, and an example
output is:
=== cctest/test-heap/TransitionArrayShrinksDuringAllocToZero ===
--- stderr ---
sem_destroy: Device busy
#
# Fatal error in ../src/base/platform/semaphore.cc, line 96
# CHECK_EQ(0, result) failed
# Expected: 0
# Found: -1
#
==== C stack trace ===============================
1: V8_Fatal
2: v8::base::Semaphore::~Semaphore()
3: v8::internal::MarkCompactCollector::~MarkCompactCollector()
4: v8::internal::Isolate::~Isolate()
5: v8::internal::Isolate::TearDown()
6: v8::Isolate::Dispose()
7: main
Command: /usr/pkgsrc/wip/v8/work/v8-4.2.14/out/ia32.debug/cctest
--random-seed=-2072276 test-heap/TransitionArrayShrinksDuringAllocToZero
--nohard-abort --nodead-code-elimination --nofold-constants
--enable-slow-asserts --debug-code --verify-heap
--testing_serialization_file=/usr/pkgsrc/wip/v8/work/v8-4.2.14/out/.serdes/serdes_TransitionArrayShrinksDuringAllocToZero
In fact, out of the 122 tests which currently fail in my test run,
109 of them seem to be exactly of this type.
This is with v8-4.2.14.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
