qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiri Danek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1540) Add options to enable Sanitizers to CMake build
Date Thu, 07 Sep 2017 07:32:00 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156617#comment-16156617

Jiri Danek commented on PROTON-1540:

Even with your options propagation fix, I still have this message coming from python-qpid-proton
tests. Which I think is completely expected. There Python starts first, and it then loads
the Proton lib when it is imported from Python code.

1: ==488==ASan runtime does not come first in initial library list; you should either link
runtime to your application or manually preload it with LD_PRELOAD.

So, ctest should be running with LD_PRELOAD, or at least the python that is running the 1:
tests, and then the sanitizer can sanitize the Python binding too.

There seem to be leaks in that. See ?? for report and what I believe is helpful command to
isolate the leaks to individual tests (otherwise all are reported at the end when Python exits).

> Add options to enable Sanitizers to CMake build
> -----------------------------------------------
>                 Key: PROTON-1540
>                 URL: https://issues.apache.org/jira/browse/PROTON-1540
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: build
>            Reporter: Jiri Danek
>            Assignee: Alan Conway
>            Priority: Minor
>              Labels: patch
>             Fix For: proton-c-0.18.0
> To get the most out of sanitizers in Qpid Dispatch, it helps to compile Proton with sanitizers
as well.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message