qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael H. Schloming (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-554) pn_data_put_long call fails on 64x Linux 2.6.32-5-amd64
Date Thu, 10 Apr 2014 15:00:31 GMT

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

Rafael H. Schloming commented on PROTON-554:

I'm afraid I haven't had much luck reproducing the issue. I don't currently have access to
a system running the same versions you are. (What distro/version are you on?) My best guess
is that it is either related to the older version of swig you are using, or that for some
reason with the particular versions in your environment some of the typedefs necessary for
swig to figure out that the given type is in fact an integral type are missing.

Would it be possible for you to try some newer versions of swig so we can try to isolate the
environmental factors that trigger the issue?

> pn_data_put_long call fails on 64x Linux 2.6.32-5-amd64
> -------------------------------------------------------
>                 Key: PROTON-554
>                 URL: https://issues.apache.org/jira/browse/PROTON-554
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: php-binding
>    Affects Versions: 0.6
>         Environment: Linux 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64
> PHP 5.4.26-1~dotdeb.0 (cli) (built: Mar  7 2014 08:58:03) 
> Copyright (c) 1997-2014 The PHP Group
> Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
>     with Xdebug v2.2.4, Copyright (c) 2002-2014, by Derick Rethans
>     with Suhosin v0.9.34-dev, Copyright (c) 2007-2012, by SektionEins GmbH
>            Reporter: Denis Savrukov
>         Attachments: qpid-proton-0.6-build.log
> Fatal error: Type error in argument 2 of pn_data_put_long. Expected SWIGTYPE_p_long_long

This message was sent by Atlassian JIRA

View raw message