[jira] [Commented] (MESOS-5887) Enhance DispatchEvent to include demangled method name.

["Benjamin Bannier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389287#comment-15389287 ] 

Benjamin Bannier commented on MESOS-5887:
-----------------------------------------

I linked MESOS-5886 to this one as these two issues are in fact closely related. There we'll likely require catching information about the actual value of the {{dispatch}}'ed member fct. It seems using the address of the member fct might be enough to uniquely identify it (but I am not 100% sure about issues from linking multiple copies).

Wouldn't we be able to build a solution on top on member fct ptrs for this issue as well? It seems that at least with glibc {{dladdr}} should give us a way to get the mangled name from fct ptr.

> Enhance DispatchEvent to include demangled method name.
> -------------------------------------------------------
>
>                 Key: MESOS-5887
>                 URL: https://issues.apache.org/jira/browse/MESOS-5887
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Alexander Rukletsov
>
> Currently, [{{DispatchEvent}}|https://github.com/apache/mesos/blob/e8ebbe5fe4189ef7ab046da2276a6abee41deeb2/3rdparty/libprocess/include/process/event.hpp#L148] does not include any user-friendly information about the actual method being dispatched. This can be helpful in order to simplify triaging and debugging, e.g., using {{\_\_processes\_\_}} endpoint. Now we print the [event type only|https://github.com/apache/mesos/blob/e8ebbe5fe4189ef7ab046da2276a6abee41deeb2/3rdparty/libprocess/src/process.cpp#L3198-L3203].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)