[
https://issues.apache.org/jira/browse/MESOS-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386743#comment-15386743
]
Benjamin Mahler commented on MESOS-5861:
----------------------------------------
[~bbannier] Is it possible to get the debugging information for libevent so
that we can have line numbers in the traces?
> Address sanitizer reports SEGV being passed to bufferevent_write_buffer
> -----------------------------------------------------------------------
>
> Key: MESOS-5861
> URL: https://issues.apache.org/jira/browse/MESOS-5861
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Affects Versions: 1.0.0
> Reporter: Benjamin Bannier
> Labels: mesosphere, ssl
> Attachments: log
>
>
> Building mesos with gcc-4.9.3 with
> {code}
> % ../configure --disable-java --disable-python --enable-silent-rules
> --enable-libevent --enable-ssl
> {code}
> with GCC address sanitizers, e.g., by adding this before the last mention of
> {{CXXFLAGS}} in {{configure.ac}},
> {code}
> % CXXFLAGS="$CXXFLAGS -fsanitize=address"
> % CCFLAGS="$CCFLAGS -fsanitize=address"
> {code}
> I am seeing reports suggested we pass bad memory to libevent functions from
> code triggered by
> libprocess' {{SSLTest}}. In particular the following tests fail:
> * {{RequireBadCA}}
> * {{SSLSocket}}
> * {{NoVerifyBadCA}}
> * {{VerifyBadCA}}
> * {{VerifyCertificate}}
> * {{ProtocolMismatch}}
> * {{HTTPSGet}}
> * {{HTTPSPost}}
> * {{SilentSocket}}
> Detailed logs are attached.
> To install gcc-4.9.3 from source one could follow the instructions in the
> configuration section [here](https://gcc.gnu.org/wiki/InstallingGCC), or
> install it from a distribution repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
