You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/03/20 02:23:15 UTC
[jira] [Created] (MESOS-406) Google mock throws a segfault when
invoked by TestFilter
Vinod Kone created MESOS-406:
--------------------------------
Summary: Google mock throws a segfault when invoked by TestFilter
Key: MESOS-406
URL: https://issues.apache.org/jira/browse/MESOS-406
Project: Mesos
Issue Type: Bug
Reporter: Vinod Kone
Assignee: Benjamin Hindman
[----------] 8 tests from SlaveRecoveryTest/1, where TypeParam = mesos::internal::slave::CgroupsIsolator
[ RUN ] SlaveRecoveryTest/1.RecoverSlaveState
I0320 00:49:14.131649 37460 master.cpp:307] Master started on 10.35.12.124:56067
I0320 00:49:14.131757 37460 master.cpp:322] Master ID: 201303200049-2081170186-56067-37439
W0320 00:49:14.131960 37459 master.cpp:79] No whitelist given. Advertising offers for all slaves
I0320 00:49:14.132063 37447 slave.cpp:202] Slave started on 1756)@10.35.12.124:56067
I0320 00:49:14.132082 37450 hierarchical_allocator_process.hpp:234] Initializing hierarchical allocator process with master : master@10.35.12.124:56067
I0320 00:49:14.132115 37447 slave.cpp:203] Slave resources: cpus=2; mem=1024; ports=[31000-32000]; disk=1024
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4780e940 (LWP 37460)]
0x0000003161208ca0 in pthread_mutex_lock () from /lib64/libpthread.so.0
(gdb) where
#0 0x0000003161208ca0 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1 0x00000000004c495b in testing::internal::MutexBase::Lock (this=0x98) at ../third_party/libprocess/third_party/gmock-1.6.0/gtest/include/gtest/internal/gtest-port.h:1208
#2 0x00000000007e1fb5 in testing::internal::GTestMutexLock::GTestMutexLock(testing::internal::MutexBase*) ()
#3 0x00000000007e878a in testing::internal::ExpectationBase::CheckActionCountIfNotDone() const ()
#4 0x000000000051ddca in FindMatchingExpectationLocked (this=0xef6208, untyped_args=0x4780dee0, untyped_action=0x4780dde0, is_excessive=0x4780ddef, what=0x4780dc80, why=0x4780db10)
at ../third_party/libprocess/third_party/gmock-1.6.0/include/gmock/gmock-spec-builders.h:1087
#5 testing::internal::FunctionMockerBase<bool ()(const process::MessageEvent&)>::UntypedFindMatchingExpectation(const void *, const void **, bool *, std::basic_ostream<char, std::char_traits<char> > *, std::basic_ostream<char, std::char_traits<char> > *) (this=0xef6208, untyped_args=0x4780dee0, untyped_action=0x4780dde0, is_excessive=0x4780ddef, what=0x4780dc80, why=0x4780db10)
at ../third_party/libprocess/third_party/gmock-1.6.0/include/gmock/gmock-spec-builders.h:1590
#6 0x00000000007e9fbe in testing::internal::UntypedFunctionMockerBase::UntypedInvokeWith(void const*) ()
#7 0x00000000004c3fa4 in InvokeWith (this=<value optimized out>, gmock_a1=...) at ../third_party/libprocess/third_party/gmock-1.6.0/include/gmock/gmock-spec-builders.h:1490
#8 Invoke (this=<value optimized out>, gmock_a1=...) at ../third_party/libprocess/third_party/gmock-1.6.0/include/gmock/gmock-generated-function-mockers.h:97
#9 mesos::internal::tests::TestsFilter::filter (this=<value optimized out>, gmock_a1=...) at ../../src/tests/filter.hpp:77
#10 0x00007ffff6ecda79 in process::ProcessManager::resume(process::ProcessBase*)::FilterVisitor::visit(process::MessageEvent const&) () from /home/vinod/mesos/build/src/.libs/libmesos-0.13.0.so
#11 0x00007ffff6ee3a48 in process::MessageEvent::visit(process::EventVisitor*) const () from /home/vinod/mesos/build/src/.libs/libmesos-0.13.0.so
#12 0x00007ffff6ed7af9 in process::ProcessManager::resume(process::ProcessBase*) () from /home/vinod/mesos/build/src/.libs/libmesos-0.13.0.so
#13 0x00007ffff6ed8444 in process::schedule(void*) () from /home/vinod/mesos/build/src/.libs/libmesos-0.13.0.so
#14 0x000000316120673d in start_thread () from /lib64/libpthread.so.0
#15 0x00000031602d3f6d in clone () from /lib64/libc.so.6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira