Hi Doug,
During the server running, coredump happened at get_ts64() of Time.cc
{
static Mutex mutex;
ScopedLock lock(mutex); // core dump
HiResTime now;
return ((uint64_t)now.sec * 1000000000LL) + (uint64_t)now.nsec;
}
infomation from gdb showed:
#0 0x00000031f3030265 in raise () from /lib64/libc.so.6
#1 0x00000031f3031d10 in abort () from /lib64/libc.so.6
#2 0x00000031f30296e6 in __assert_fail () from /lib64/libc.so.6
#3 0x00000000005cea20 in boost::mutex::lock (this=0xa52a00)
at
/home/onest/BC_ONEST_BETA_20100715_14/build/thirdpart/include/boost/thread/pthread/mutex.hpp:50
#4 0x00000000005cea90 in boost::unique_lock<boost::mutex>::lock
(this=0x601d5e50)
at
/home/onest/BC_ONEST_BETA_20100715_14/build/thirdpart/include/boost/thread/locks.hpp:338
#5 0x00000000005ceacc in unique_lock (this=0x601d5e50, m...@0xa52a00)
at
/home/onest/BC_ONEST_BETA_20100715_14/build/thirdpart/include/boost/thread/locks.hpp:224
and mutex state was printed:
$2 = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind =
-1, __spins = 0, __list = {__prev = 0x0,
__next = 0x0}}, __size = '\0' <repeats 16 times>, "яяяя", '\0'
<repeats 19 times>, __align = 0}:
and Doug, I questions about whether the get_ts64() must have the mutex to
ensure reentrance.
Is boost::xtime_get(...) thread-safe, isn't it?
Thanks.
Alen
--
You received this message because you are subscribed to the Google Groups
"Hypertable Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hypertable-dev?hl=en.
