Valgrind which is good at showing the stack when the error happens. I
won't have time to look into it for a bit.
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/activemq-cpp-problem-when-openssl-enabled-tp4661580p4661657.html
> Sent from
equency of crash is much lower.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-cpp-problem-when-openssl-enabled-tp4661580p4661657.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ges to the
threading in there. Most likely the issue is that a thread is trying to
run some error handling code but its parent got deleted to early.
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/activemq-cpp-problem-when-openssl-enabled-tp466
ual happens when syncObject->lock() called. I am guessing the
syncObject might be an corrupted pointer.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-cpp-problem-when-openssl-enabled-tp4661580p4661633.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
from, I could not catch it in my test
> code, I am guessing it's deep in library. Any suggestion to avoid the
> problem?
>
> Thanks
>
> Alex
>
> Thanks for help,
>
> A
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n
e in context:
http://activemq.2283324.n4.nabble.com/activemq-cpp-problem-when-openssl-enabled-tp4661580.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
