Hi Tim, The "throw()" that I'm talking about it because the API has changed between activemq-cpp 3.1.x and activemq-cpp 3.4. Now (3.4) the signature of the onMessage method and the destructor of the MessageListener expect to throw an exception which was not the case previously.
So I was wondering if a #defined was added when that API has changed, so I can use it in my code to support any version of activemq-cpp. Regarding, the trunk, on my Mac/Lion my application is still not functional, but as I don't have any minimal use case, I will let that on the side for now. Thanks again, Seb On Tue, Aug 9, 2011 at 6:10 PM, tabish...@gmail.com [via ActiveMQ] <ml-node+3731429-1427594448-258...@n4.nabble.com> wrote: > On Tue, 2011-08-09 at 14:57 -0700, Seb wrote: >> Hi Tim, >> >> So I give a try on Linux Ubuntu 9.4 with gcc 4.4.1 with the svn trunk >> of activemq-cpp. >> >> I still get the same runtime error in the "createThreadInstance" with >> the sample code. >> >> Although, when I use my code with the fix ( "throw()" added), it works >> just fine. >> >> So I have 3 questions: >> - what is the test that you are doing to validate that activemq-cpp is >> fully working on the different targeted platform. >> - what version should I use if my application target all Unix platform >> ? (Mac OS X (Leo, Snow Leo, Lion), Linux) >> - Is there any #define that I can use to add dynamically that >> "throw()" in my code based on a #ifdef >> >> Anyway, thanks for your help, >> >> Seb >> >> > If using a plain linux box then I'd use v3.4.0 as trunk is generally > unstable. > > Don't know what throw() change you are making. > > For Mac trunk has the fixes needed for building on Mac which you could > backport to 3.4.0. Once done then the unit and integration tests can be > run to validate. > > 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-tp3730337p3731429.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-tp3730337p3731462.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.