You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Manuel Teira (JIRA)" <qp...@incubator.apache.org> on 2008/06/02 11:39:46 UTC

[jira] Updated: (QPID-1108) QPID broker asserts in qpid::sys::RWlock::RWlock()

     [ https://issues.apache.org/jira/browse/QPID-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manuel Teira updated QPID-1108:
-------------------------------

    Attachment: mutex-fix.patch

This patch deletes the initialization machinery for RWlock, since we don't need it to use just default attributes in pthread_rwlock_init. Furthermore, reusing the same pthread_once_t attribute will lead to unitialized values in Mutex or RWlock, depending on the first one to be called.



> QPID broker asserts in qpid::sys::RWlock::RWlock()
> --------------------------------------------------
>
>                 Key: QPID-1108
>                 URL: https://issues.apache.org/jira/browse/QPID-1108
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: M3
>         Environment: Solaris 10 OS on UltraSparc hw
>            Reporter: Manuel Teira
>         Attachments: mutex-fix.patch
>
>
> Creation of a RWlock asserts in the call:
> QPID_POSIX_ASSERT_THROW_IF(pthread_rwlock_init(&rwlock, recursiveRWlockattr));
> As discussed in the dev maillist, the problem is reusing the pthread_once_t variable to initialize both the RWlock and Mutex initialization attrs. Furthermore, this machinery is not even needed for RWlock, as default attributes would suffice.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.