Segmentation fault when unloading shared libraries linked with libqpidmessaging
-------------------------------------------------------------------------------
Key: QPID-3364
URL: https://issues.apache.org/jira/browse/QPID-3364
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.10, 0.8, 0.11
Environment: Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1)
(da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18
07:08:50 UTC 2011
Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011
Reporter: Paul Colby
Priority: Minor
Disclaimer: I'm not a dlopen/dlclose expert... I'm perfectly happy to be told
that I don't know what I'm doing! ;)
If I create a shared object (that may or may not implement anything) that links
with libqpidmessaging (ie g++ ... -lqpidmessaging), and then create an
application that dlopen's that library, then dlclose's that library, then that
application will cause a seg-fault, which appears to be in the libqpidmessaging
library itself.
To demonstrate, I have a loadee.cpp file that contains just the following
unimportant code:
{quote}
void foo() { }
{quote}
Then I build a loadee.so shared object like:
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
