[
https://issues.apache.org/activemq/browse/AMQCPP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-203:
-------------------------------------
Attachment: weekend.puzzle.tar.gz
(Do you recall why everybody feared Gandalf? He was the kill-joy bringing bad
news... don't hate me too much) :(
Two segmentation faults, at apr-cleanup and dsm->looseMarshaller. I decided not
to stop the run to see if I can repeat the latest AMQCPP-202.
I've included some prints this time, but I realized too late that I was not
echoing the input, so they're not easy to follow at a first glance. I can
repeat that on Monday (have to baby sitting tonight and I'm running out of
time). My $.02 - that's actually the worth it:
core.5523: plain_cleanup_fn is invalid (-2). (Casting problem or premature
deletion?)
core.19005: While dsm->looseMarshaller: dsm seems to be just deleted as it is
no longer at dataMarshallers[type=1] (who else is messing with the
dataMarshallers array?). A thread switch between lines 167 and 197 - weired,
huh?
I know we can. I just wish we were already there. ;)
> 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, 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.
