You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by kkreja <Kr...@compuware.com> on 2010/07/19 16:01:29 UTC
activemq-cpp 3.2.0 Segmentation fault on 32 bit but not on 64bit
Hi,
I upgraded from activemq-cpp 3.1.2 to 3.2.0 and I get a Segmentation fault
every time I run my app. I get it even running the example from the
activemq-cpp site (http://activemq.apache.org/cms/example.html).
the stack trace looks like that:
#0 0x002424c7 in apr_atomic_add32 (mem=0x889d09c, val=4294967295) at
atomic/unix/mutex.c:78
#1 0x00ccba88 in
decaf::util::concurrent::atomic::AtomicInteger::decrementAndGet
(this=0x889d098)
at decaf/util/concurrent/atomic/AtomicInteger.cpp:69
#2 0x00c89208 in decaf::lang::ArrayPointer<unsigned char,
decaf::util::concurrent::atomic::AtomicRefCounter>::reset (
this=0xbf8af538, value=0x889d9b8 "\177", size=4) at
./decaf/util/concurrent/atomic/AtomicRefCounter.h:68
#3 0x00c88e2c in InetAddress (this=0xbf8af52c, hostname=@0xbf8af564,
ipAddress=0xd0b43b "\177", numBytes=4)
at decaf/net/InetAddress.cpp:79
#4 0x00c861c7 in Inet4Address (this=0xbf8af52c, hostname=@0xbf8af564,
ipAddress=0xd0b43b "\177", numBytes=4)
at decaf/net/Inet4Address.cpp:34
#5 0x00c87243 in __static_initialization_and_destruction_0
(__initialize_p=<value optimized out>,
__priority=<value optimized out>) at decaf/net/InetAddress.cpp:39
#6 0x00ce2396 in __do_global_ctors_aux () from
/usr/lib/activemq-cpp-3.2.0/libactivemq-cpp.so.12
#7 0x0081064d in _init () from
/usr/lib/activemq-cpp-3.2.0/libactivemq-cpp.so.12
#8 0x002a01e3 in call_init () from /lib/ld-linux.so.2
#9 0x002a02f3 in _dl_init_internal () from /lib/ld-linux.so.2
#10 0x0029284f in _dl_start_user () from /lib/ld-linux.so.2
I get it only on a 32bit system. On 64 bit everything works perfectly fine.
Any clues, what I'm doing wrong?
--
View this message in context: http://old.nabble.com/activemq-cpp-3.2.0-Segmentation-fault-on-32-bit-but-not-on-64bit-tp29205034p29205034.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: activemq-cpp 3.2.0 Segmentation fault on 32 bit but not on
64bit
Posted by Timothy Bish <ta...@gmail.com>.
On Mon, 2010-07-19 at 07:24 -0700, kkreja wrote:
> >These fixes will be included in the next patch release v3.2.2
>
> Great news.
>
> Is the date for the 3.2.2 release known yet?
>
> Regards
>
> Krzysztof Kreja
No date yet, probably be another couple weeks in order to allow time for
more issues to be reported and fixed.
Regards
--
Tim Bish
Open Source Integration: http://fusesource.com
ActiveMQ in Action: http://www.manning.com/snyder/
Follow me on Twitter: http://twitter.com/tabish121
My Blog: http://timbish.blogspot.com/
Re: activemq-cpp 3.2.0 Segmentation fault on 32 bit but not on
64bit
Posted by kkreja <Kr...@compuware.com>.
>These fixes will be included in the next patch release v3.2.2
Great news.
Is the date for the 3.2.2 release known yet?
Regards
Krzysztof Kreja
--
View this message in context: http://old.nabble.com/activemq-cpp-3.2.0-Segmentation-fault-on-32-bit-but-not-on-64bit-tp29205034p29205252.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: activemq-cpp 3.2.0 Segmentation fault on 32 bit but not on
64bit
Posted by Timothy Bish <ta...@gmail.com>.
On Mon, 2010-07-19 at 07:01 -0700, kkreja wrote:
> Hi,
>
> I upgraded from activemq-cpp 3.1.2 to 3.2.0 and I get a Segmentation fault
> every time I run my app. I get it even running the example from the
> activemq-cpp site (http://activemq.apache.org/cms/example.html).
>
> the stack trace looks like that:
>
> #0 0x002424c7 in apr_atomic_add32 (mem=0x889d09c, val=4294967295) at
> atomic/unix/mutex.c:78
> #1 0x00ccba88 in
> decaf::util::concurrent::atomic::AtomicInteger::decrementAndGet
> (this=0x889d098)
> at decaf/util/concurrent/atomic/AtomicInteger.cpp:69
> #2 0x00c89208 in decaf::lang::ArrayPointer<unsigned char,
> decaf::util::concurrent::atomic::AtomicRefCounter>::reset (
> this=0xbf8af538, value=0x889d9b8 "\177", size=4) at
> ./decaf/util/concurrent/atomic/AtomicRefCounter.h:68
> #3 0x00c88e2c in InetAddress (this=0xbf8af52c, hostname=@0xbf8af564,
> ipAddress=0xd0b43b "\177", numBytes=4)
> at decaf/net/InetAddress.cpp:79
> #4 0x00c861c7 in Inet4Address (this=0xbf8af52c, hostname=@0xbf8af564,
> ipAddress=0xd0b43b "\177", numBytes=4)
> at decaf/net/Inet4Address.cpp:34
> #5 0x00c87243 in __static_initialization_and_destruction_0
> (__initialize_p=<value optimized out>,
> __priority=<value optimized out>) at decaf/net/InetAddress.cpp:39
> #6 0x00ce2396 in __do_global_ctors_aux () from
> /usr/lib/activemq-cpp-3.2.0/libactivemq-cpp.so.12
> #7 0x0081064d in _init () from
> /usr/lib/activemq-cpp-3.2.0/libactivemq-cpp.so.12
> #8 0x002a01e3 in call_init () from /lib/ld-linux.so.2
> #9 0x002a02f3 in _dl_init_internal () from /lib/ld-linux.so.2
> #10 0x0029284f in _dl_start_user () from /lib/ld-linux.so.2
>
> I get it only on a 32bit system. On 64 bit everything works perfectly fine.
>
> Any clues, what I'm doing wrong?
This is related to a couple of bugs that were reported last week and
have been fixed in the 3.2.x fixes branch. You can check out a copy of
the code from here:
svn co
https://svn.apache.org/repos/asf/activemq/activemq-cpp/branches/activemq-cpp-3.2.x
These fixes will be included in the next patch release v3.2.2
Regards
--
Tim Bish
Open Source Integration: http://fusesource.com
ActiveMQ in Action: http://www.manning.com/snyder/
Follow me on Twitter: http://twitter.com/tabish121
My Blog: http://timbish.blogspot.com/