mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Chen" <>
Subject Re: Review Request 28052: Match future dispatch messages with type info.
Date Tue, 18 Nov 2014 06:35:18 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Nov. 18, 2014, 6:35 a.m.)

Review request for mesos, Benjamin Hindman and Ben Mahler.

Bugs: MESOS-2112

Repository: mesos-git

Description (updated)


The fix in this rb is to instead of matching pointer values, but to compare type_info from
the member function pointers passed in. This ensures we're matching the same method.

The downside of this approach is that, we no longer can do the following in tests:

class A : ProcessBase<A> {
  virtual void foo() {};

class B : public A {
  virtual void foo() {};

Future<Nothing> future = FUTURE_DISPATCH(_, &B::foo);

process.dispatch(B.self(), &A::foo);



We no longer can match the future on a derived method, but on dispatch passing the base member
function pointer. This only used to work since the virtual offsets of both is matching the
same address, but arguable is not the right behavior since the reverse is a false positive
but will also match. We've done this in a few places in tests around the AllocatorProcess.


  3rdparty/libprocess/include/process/c++11/dispatch.hpp 76da2828cf36b6143d627dac66f3e0cc4416bae4

  3rdparty/libprocess/include/process/dispatch.hpp bceda2a2ae8963921e8e19660243a8644feab227

  3rdparty/libprocess/include/process/event.hpp 294e2158876b25b06456a3619e547082d71e31ed 
  3rdparty/libprocess/include/process/gmock.hpp d6f2fc8fef8acd1498a36c86e09b28d986eefa15 
  3rdparty/libprocess/src/process.cpp 404a32dae1b3d22cb55dcbd084623d6b0cb82c71 



make check


Timothy Chen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message