Thanks all that's exactly the fix for me.
It makes sense now that I've read
https://issues.apache.org/jira/browse/AMQCPP-369
https://issues.apache.org/jira/browse/AMQCPP-369 . I've tested it on Fedora
16 x86_64 and i686 and it works on both platforms.
Back in my coding days I would have see
2011/12/2 Timothy Bish :
> If you are using a mac then you need to get the 3.4. SNAPSHOT code from the
> link on the v3.4.1 download page.
The same issue (https://issues.apache.org/jira/browse/AMQCPP-369) is
applicable to Solaris too.
So, it's not Mac-specific at all, and I suggest to try 3.4.1 on
Thanks. I'm using Fedora 16 on bare metal (no VM). Naturally I'd much
rather be using my Mac but that's mostly occupied by my wife and kids! On
reading a few other things on the net it would appear that this is not
unusual for the 64bit operating system. I'm going to run up a 32bit VM and
see i
If you are using a mac then you need to get the 3.4. SNAPSHOT code from the
link on the v3.4.1 download page.
On Thu, Dec 1, 2011 at 6:32 PM, stretch_kiwi <
mich...@chesterproductions.net.nz> wrote:
> Seems that its segfaulting on a futex
>
> futex(0x336e2f2fb0, FUTEX_WAKE_PRIVATE, 2147483647) =
Seems that its segfaulting on a futex
futex(0x336e2f2fb0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
--- {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xfff8}
(Segmentation fault) ---
+++ killed by SIGSEGV (core dumped) +++
--
View this message in context:
http://activemq.2283324.n4.nabb
Thank you for the suggestion. Unfortunately while it claims that it dumped a
core, strangely I can't find it! At first I thought the limits had been set
(as in ulimit -c 0).
[michael@blackbox test]$ ulimit -a
core file size (blocks, -c) 1
data seg size (kbytes, -d) unlimit
2011/12/2 stretch_kiwi :
> [michael@blackbox test]$ ./activemq-test
> Segmentation fault (core dumped)
> I would appreciate any practical suggestions.
Stack backtrace should be the first thing to look at:
$ gdb activemq-test core
> where
