qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-442) Running swig generates "Warning(451): Setting a const char * variable may leak memory."
Date Mon, 21 Oct 2013 17:14:45 GMT

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

ASF subversion and git services commented on PROTON-442:
--------------------------------------------------------

Commit 1534282 from [~fadams] in branch 'proton/trunk'
[ https://svn.apache.org/r1534282 ]

JIRA: PROTON-442 PROTON-442: When building proton I get Warning Setting a const char * variable
may leak memory. should really strive for a clean build.

> Running swig generates "Warning(451): Setting a const char * variable may leak memory."
> ---------------------------------------------------------------------------------------
>
>                 Key: PROTON-442
>                 URL: https://issues.apache.org/jira/browse/PROTON-442
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.5
>            Reporter: Fraser Adams
>            Priority: Minor
>
> When building proton after doing cmake .. the make process is quite "noisy" generating
a number of warnings that ought to be corrected.
> One such warning is:
> "Warning(451): Setting a const char * variable may leak memory."
> This relates to the "const char *bytes;" in the pn_delivery_tag_t struct in engine.h
> The swig documentation in http://www.swig.org/Doc1.3/Warnings.html suggests how to suppress
this warning (due to the way the code works I believe that it's safe to suppress this case)
by doing:
> %warnfilter(451) pn_delivery_tag_t;
> in the various python.i, perl.i etc.
> I've make the changes locally and this indeed works.
> I'll put together a review board request.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message