Re: ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization

2014-03-26 Thread Nikolaus Klimek
Thank you for your prompt response! Our Problem seems to be solved. The Solution in our case was to change the dlopen() call. We added the flag RTLD_DEEPBIND and it seems to work. Thanks a lot for your hints! Regards Niko 2014-03-13 13:41 GMT+02:00 artnaseef : > Hmm, a segfault in std::basic_st

Re: ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization

2014-03-13 Thread artnaseef
Hmm, a segfault in std::basic_string points to something troubling. Two ideas coming to mind - the library is not being initialized properly, or there is corruption earlier (probably due to pointer problems) that's causing this later call to fail. In the case of initialization not being correct -

Re: ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization

2014-03-13 Thread Nikolaus Klimek
Sorry for the late response. I know we have a special sort of scenario, but maybe you can help us. I did some debugging, here are some informations: Program terminated with signal 11, Segmentation fault. #0 0x03fffb2fa2d4 in std::basic_string, std::allocator >::basic_string() () from /usr/lib

Re: ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization

2013-12-05 Thread Timothy Bish
On 12/05/2013 02:57 AM, Nikolaus Klimek wrote: Hello, because our previous SLES Version does not support required apr-version, we used the ActiveMQ C++ Client 2.2.6, which was compiled to a shared object/library and called by a cobol application (via CALL). This combination works fine. Actually

ActiveMQ C++ higher Version 2.2.6 - Segfault by initialization

2013-12-04 Thread Nikolaus Klimek
Hello, because our previous SLES Version does not support required apr-version, we used the ActiveMQ C++ Client 2.2.6, which was compiled to a shared object/library and called by a cobol application (via CALL). This combination works fine. Actually we updated our SLES (to 11.2) and a higher apr-v