[
https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-203:
-------------------------------------
Attachment: segfault.6517.tar.gz
Hi!
A new deadlock and a new segmentation fault.
* The deadlock took place during a lock call to a presumably released mutex
(DecafRuntime destructor).
* The segmentation fault, while std::size_t available =
inputStream->available(); (ex = NULL?!)
There are some other ugly messages at the output (an error at #87 and an
exception at the bottom).
As always, I let the process running, just in case you want to peek any
variable.
Hope this helps.
> Segmentation Fault in Integration tests occurs occasionally.
> ------------------------------------------------------------
>
> Key: AMQCPP-203
> URL: https://issues.apache.org/activemq/browse/AMQCPP-203
> Project: ActiveMQ C++ Client
> Issue Type: Sub-task
> Components: Integration Tests
> Affects Versions: 2.2.1
> Environment: CentOS 5.2 / REHL / Fedora 9
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 2.2.2
>
> Attachments: BufferedInputStream.cpp.patch, segfault.6517.tar.gz,
> segfault.bufferedinputstream.log.gz, segfaults.barak.tar.gz, segfaults.tar.gz
>
>
> While running the integration tests in a long loop an occasional Segmentation
> fault has been seen.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
