You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Christian Warmuth (JIRA)" <ji...@apache.org> on 2010/03/08 10:35:45 UTC

[jira] Issue Comment Edited: (AMQCPP-273) Segmentation violation after pure virtual method called in tempdest_advisory_producer example

    [ https://issues.apache.org/activemq/browse/AMQCPP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58082#action_58082 ] 

Christian Warmuth edited comment on AMQCPP-273 at 3/8/10 9:34 AM:
------------------------------------------------------------------

Same problem in tempdest_advisory_producer example.

Found in branch 3.1.x

The fix was added for tempdet_advisory_consumer only.

      was (Author: chrism3):
    Same problem in tempdest_advisory_producer example.

Found in branch 3.1.x
  
> Segmentation violation after pure virtual method called in tempdest_advisory_producer example
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-273
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-273
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.1
>         Environment: CentOS 5.4 x86_64 with kernel 2.6.18-164.el5.
> activemq-cpp compiled with gcc version 4.1.2.
>            Reporter: Arjan van den Berg
>            Assignee: Timothy Bish
>             Fix For: 3.1.1
>
>
> To reproduce:
> make check
> cd src/examples
> run tempdest_advisory_producer.
> Result:
> =====================================================
> Starting the example:
> -----------------------------------------------------
> -----------------------------------------------------
> Finished with the example.
> =====================================================
> pure virtual method called
> terminate called without an active exception
> Aborted
> Sometimes also the following is printed:
> pure virtual method called
> terminate called after throwing an instance of 'decaf::io::IOException'
>   what():  DataInputStream::readLong - Reached EOF
> gdb backtrace (generated with libtool gdb tempdest_advisory_producer):
> (gdb) bt
> #0  0x00002b9159a6855a in Lock (this=0x44bc9080, object=0x747d510,
>     intiallyLocked=true) at ./decaf/util/concurrent/Lock.h:96
> #1  0x00002b9159da8558 in decaf::lang::ThreadProperties::runCallback (
>     properties=0x747d4b0) at decaf/lang/Thread.cpp:157
> #2  0x00002b9159da5d2b in threadWorker (arg=0x747d4b0)
>     at decaf/lang/Thread.cpp:186
> #3  0x00002b915ae15617 in start_thread () from /lib64/libpthread.so.0
> #4  0x00002b915b590c2d in clone () from /lib64/libc.so.6

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.