[
https://issues.apache.org/jira/browse/MESOS-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296128#comment-14296128
]
Cody Maloney commented on MESOS-2144:
-------------------------------------
Based on the addresses being at the low end of the address range I'm guessing
it is happening while running __cxa_exit (global static destruction), or some
other system cleanup symbol and this is during glibc doing something on mesos'
behalf. Likely whatever that library is doesn't have symbols / is stripped if
it is coming from the Linux distribution.
Side note:
Backtraces from our code don't use the debugging info. But yea, definitely
looks like debugging is enabled. And functions shouldn't be optimized, binary
isn't stripped of symbols, so stack traces should have all the function symbols.
> Segmentation Fault in ExamplesTest.LowLevelSchedulerPthread
> -----------------------------------------------------------
>
> Key: MESOS-2144
> URL: https://issues.apache.org/jira/browse/MESOS-2144
> Project: Mesos
> Issue Type: Bug
> Components: test
> Affects Versions: 0.21.0
> Reporter: Cody Maloney
> Priority: Minor
> Labels: flaky
>
> Occured on review bot review of:
> https://reviews.apache.org/r/28262/#review62333
> The review doesn't touch code related to the test (And doesn't break
> libprocess in general)
> [ RUN ] ExamplesTest.LowLevelSchedulerPthread
> ../../src/tests/script.cpp:83: Failure
> Failed
> low_level_scheduler_pthread_test.sh terminated with signal Segmentation fault
> [ FAILED ] ExamplesTest.LowLevelSchedulerPthread (7561 ms)
> The test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
