[
https://issues.apache.org/activemq/browse/AMQCPP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Martens updated AMQCPP-200:
-------------------------------------
Attachment: more.daemons.tar.gz
Sorry for the late answer - still fighting too many battles at a time.
Yes, your latest changes were (excepting a !closed in the manager) on the
integration tests (they've been nearly rewritten). Testing results, are
therefore different too (shouldn't be, but they seem to be).
The short version says:
Segmentation fault on iteration #16: dsm->looseMarshal( this, dataStructure,
looseOut ); (core.14475)
Segmentation fault on iteration #36: std::size_t available =
inputStream->available(); (core.19442)
Locked on iteration #65
I do also include the output.log, server's log (which is interesting this time;
some errors since second 1 or so) and gdb outputs...
BTW: I commented stomp tests out again, just to narrow searches.
Hope this helps!
> activemq-cpp-2.2.1 test fails for
> decaf::io::ByteArrayInputStreamTest::testConstructor (segmentation fault)
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMQCPP-200
> URL: https://issues.apache.org/activemq/browse/AMQCPP-200
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Decaf
> Affects Versions: 2.2.1
> Environment: RHEL 5.2 (2.6.18-92.el5), apr-1.3.3, apr-util-1.3.4,
> cppunit-1.12.1, gcc version 4.1.2 20071124 (Red Hat 4.1.2-42), Java(TM) SE
> Runtime Environment (build 1.6.0_06-b02)
> Reporter: Alexander Martens
> Assignee: Timothy Bish
> Fix For: 2.2.2
>
> Attachments: CentOS-AprPool-Fix-Test.patch, daemons.1.tar.gz,
> deadlock.6.tar.gz, deadlock.7.log.gz, deadlock.8.log.gz, deadlock.9.tar.gz,
> deadlock.log.gz, deadlock.openwire.join.tar.gz, deadlock2.log.gz,
> more.daemons.tar.gz, openwire_transaction.tar.gz, quota.2.tar.gz,
> seg_fault.log.gz, setup.tar.gz, storage_logs.tar.gz,
> testConstructor-O0.log.gz, testConstructor.log.gz, testString-O0.log.gz
>
>
> This unit test seems to fail.
> I send you attached a gdb postmortem log (bt, bt full, info threads).
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
