On Tue, 2011-08-09 at 13:41 -0700, Seb wrote: > Hi Tim, > > thanks for your reply. > So my platform in both case is Mac OS X Lion (10.7) with gcc 4.2. > > When I tried to compiled the trunk, the compilation of the demo sample > complain here: > > /.../src/main.cpp:108: error: cannot call member function ‘long long > int decaf::lang::Thread::getId() const’ without object > > That I've fixed by doing that instead: > > string threadIdStr = Integer::toString( Thread::currentThread()->getId() ); > > And the result is also a segfault. > > Here is the stack trace
The history on Mac and AMQCPP is not so good, no testing on Lion so far as I don't have it installed, I know it was working on Snow Leopard at one time. You can try it out in a Linux VM and it should work. Regards > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000040 > decaf::internal::util::concurrent::Threading::createNewThread > (parent=0x7fff5fbffa68, name=0x100e18588 "Thread-1", stackSize=-1) at > Threading.cpp:316 > 316 &thread->threadId); > (gdb) bt > #0 decaf::internal::util::concurrent::Threading::createNewThread > (parent=0x7fff5fbffa68, name=0x100e18588 "Thread-1", stackSize=-1) at > Threading.cpp:316 > #1 0x00000001002b2f17 in decaf::lang::Thread::initializeSelf > (this=0x7fff5fbffa68, task=0x7fff5fbffa88, name=@0x100e18a80, > stackSize=-1) at Thread.cpp:125 > #2 0x00000001002b31a2 in decaf::lang::Thread::Thread > (this=0x7fff5fbffa68, task=0x100e18591) at Thread.cpp:94 > #3 0x0000000100001c0a in main (argc=1, argv=0x7fff5fbffbd8) at main.cpp:382 > > Thanks for any help, > > Seb > > On Tue, Aug 9, 2011 at 4:22 PM, tabish...@gmail.com [via ActiveMQ] > <ml-node+3731143-722528546-258...@n4.nabble.com> wrote: > > On Tue, 2011-08-09 at 13:14 -0700, Seb wrote: > >> I'm going to partially answer to my question. > >> The issue that I was facing is related to the following bug > >> https://issues.apache.org/jira/browse/AMQCPP-369 > >> > >> By patching activemq-cpp 3.4 with the change made for that bug fix, I > >> managed to compile and run the application. > >> > >> But with the demo application now I get the following errors. > >> > >> ===================================================== > >> Starting the example: > >> ----------------------------------------------------- > >> No Matching Factory Registered for format := tcp > >> FILE: activemq/transport/TransportRegistry.cpp, LINE: 44 > >> FILE: activemq/core/ActiveMQConnectionFactory.cpp, LINE: 325 > >> No Matching Factory Registered for format := tcp > >> FILE: activemq/transport/TransportRegistry.cpp, LINE: 44 > >> FILE: activemq/core/ActiveMQConnectionFactory.cpp, LINE: 325 > >> Time to completion = 20 seconds. > >> ----------------------------------------------------- > >> Finished with the example. > >> ===================================================== > >> > >> Moreover, when I try my application, it simply hang. So I would say that > >> I'm > >> still facing some issue which prevent me from using that version of the > >> library. > >> > >> If someone as a sample code that work with activemq-cpp 3.4, I would be > >> happy to give a try on my laptop. > >> > >> Any help or idea would be great. > >> > > What is the platform OS and compiler you are using? Have you tried the > > code from CMS trunk? > > > > Regards > > > > > > > > -- > > Tim Bish > > ------------ > > FuseSource > > Email: [hidden email] > > Web: http://fusesource.com > > Twitter: tabish121 > > Blog: http://timbish.blogspot.com/ > > > > > > > > > > > > ________________________________ > > If you reply to this email, your message will be added to the discussion > > below: > > http://activemq.2283324.n4.nabble.com/Segfault-with-ActiveMQ-CPP-3-4-0-tp3730337p3731143.html > > To unsubscribe from Segfault with ActiveMQ-CPP 3.4.0, click here. > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Segfault-with-ActiveMQ-CPP-3-4-0-tp3730337p3731196.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
