[
https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-203:
-------------------------------------
Attachment: segfault.29505.log.gz
Another interesting one (loop #287, in testBasic):
A coincidence _Unwind_Find_FDE and __deallocate_stack seems to cause a
segmentation fault.
I can't dig that deep without debug symbols (unless you see something trivial
at a higher level).
Some prints appended.
The good new is that nothing bad happened during the previous 287 tries. 8)
I'll let it running during the whole night.
> 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.29505.log.gz,
> segfault.6517.tar.gz, segfault.bufferedinputstream.log.gz,
> segfaults.barak.tar.gz, segfaults.tar.gz, weekend.puzzle.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.
