You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/06/26 04:46:01 UTC

[jira] [Comment Edited] (MESOS-7160) Parsing of perf version segfaults

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

James Peach edited comment on MESOS-7160 at 6/26/17 4:45 AM:
-------------------------------------------------------------

I ran into this in a VM dev environment, and one way this can happen is due to a race with the use of {{Subprocess::ChildHook::SUPERVISOR}}. If {{perf}} is not installed, then the {{execv}} will fail, and this can happen before the supervisor parent process calls {{waitpid}}. Then {{waitpid}} returns -1 (with {{ESRCH}} and the supervisor calls {{abort()}}.


was (Author: jamespeach):
I looked

> Parsing of perf version segfaults
> ---------------------------------
>
>                 Key: MESOS-7160
>                 URL: https://issues.apache.org/jira/browse/MESOS-7160
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>            Reporter: Benjamin Bannier
>
> Parsing the perf version [fails with a segfault in ASF CI|https://builds.apache.org/job/Mesos-Buildbot/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/3294/],
> {noformat}
> E0222 20:54:03.033464   805 perf.cpp:237] Failed to get perf version: Failed to execute perf: terminated with signal Aborted (core dumped)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)