You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Shearer, Davin" <ds...@novetta.com> on 2014/01/20 15:50:27 UTC
void qpid::sys::Mutex::lock(): Assertion `0' failed
Just loading the amqp.so and asking for help causes an assertion failure.
[davin@laptop24 qpid]$ usr/local/sbin/qpidd
--load-module=/home/davin/stash/exit2xx/external/qpid/qpid/usr/local/lib64/qpid/daemon/amqp.so
--help
Usage: qpidd [OPTIONS]
Options:
-h [ --help ] Displays the help message
-v [ --version ] Displays version information
--config FILE (/usr/local/etc/qpid/qpidd.conf)
Reads configuration from FILE
--client-config FILE (/usr/local/etc/qpid/qpidc.conf)
Reads client configuration from
FILE
(for cluster interconnect)
Module options:
--module-dir DIR (/usr/local/lib64/qpid/daemon)
Load all shareable modules in this
directory
... more help here ...
-q [ --quit ] Tells the daemon to shut down
AMQP 1.0 Options:
--domain DOMAIN Domain of this broker
--queue-patterns PATTERN Pattern for on-demand queues
--topic-patterns PATTERN Pattern for on-demand topics
Invalid argument
qpidd:
/home/davin/stash/exit2xx/external/qpid/build/cpp/src/qpid/sys/posix/Mutex.h:116:
void qpid::sys::Mutex::lock(): Assertion `0' failed.
Aborted (core dumped)
Backtrace:
#0 0x00000037c84359e9 in raise () from /lib64/libc.so.6
#1 0x00000037c84370f8 in abort () from /lib64/libc.so.6
#2 0x00000037c842e956 in __assert_fail_base () from /lib64/libc.so.6
#3 0x00000037c842ea02 in __assert_fail () from /lib64/libc.so.6
#4 0x0000000000668f22 in qpid::sys::Mutex::lock() ()
#5 0x0000000000668fa4 in
qpid::sys::ScopedLock<qpid::sys::Mutex>::ScopedLock(qpid::sys::Mutex&) ()
#6 0x00000000008b0048 in
qpid::sys::DeletionManager<qpid::sys::PollerHandlePrivate>::AllThreadsStatuses::~AllThreadsStatuses()
()
#7 0x00000037c8439279 in __run_exit_handlers () from /lib64/libc.so.6
#8 0x00000037c84392c5 in exit () from /lib64/libc.so.6
#9 0x00000037c8421b4c in __libc_start_main () from /lib64/libc.so.6
#10 0x0000000000648389 in _start ()
--
Davin Shearer
Re: void qpid::sys::Mutex::lock(): Assertion `0' failed
Posted by "Shearer, Davin" <ds...@novetta.com>.
Hi Gordon,
Yes, this is with the static link changes (static link against boost
v1.55.0 and proton v0.6 and the broker static link against libqpid*.a).
I've run this on Fedora19 and Centos6.5, the results are the same.
Great question, I just tried loading xml.so, store.so and ha.so and they
also fail the same assertion.
That gives us a little more to go on.
On Tue, Jan 21, 2014 at 8:32 AM, Gordon Sim <gs...@redhat.com> wrote:
> On 01/20/2014 02:50 PM, Shearer, Davin wrote:
>
>> Just loading the amqp.so and asking for help causes an assertion failure.
>>
>
> I assume this with the static linking changes? If not, what platform are
> you building on?
>
> Does it only happen when loading the amqp.so module? Or does it happen
> when any module is loaded?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
Davin Shearer
Engineer
8830 Stanford Blvd, Suite 306
Columbia, MD 21045
443-741-4517
Re: void qpid::sys::Mutex::lock(): Assertion `0' failed
Posted by Gordon Sim <gs...@redhat.com>.
On 01/20/2014 02:50 PM, Shearer, Davin wrote:
> Just loading the amqp.so and asking for help causes an assertion failure.
I assume this with the static linking changes? If not, what platform are
you building on?
Does it only happen when loading the amqp.so module? Or does it happen
when any module is loaded?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: void qpid::sys::Mutex::lock(): Assertion `0' failed
Posted by "Shearer, Davin" <ds...@novetta.com>.
Here's the last bit of an strace of the same command:
...
write(1, " --topic-patterns PATTERN Patt"..., 57 --topic-patterns
PATTERN Pattern for on-demand topics
) = 57
write(1, "\n", 1
) = 1
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 2), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f1222ea0000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "Invalid argument\n", 17Invalid argument
) = 17
close(3) = 0
munmap(0x7f1222ea0000, 4096) = 0
write(2, "qpidd: /home/davin/stash/exit2xx"..., 142qpidd:
/home/davin/stash/exit2xx/external/qpid/build/cpp/src/qpid/sys/posix/Mutex.h:116:
void qpid::sys::Mutex::lock(): Assertion `0' failed.
) = 142
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f1222ea0000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(30725, 30725, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=30725, si_uid=1011}
---
+++ killed by SIGABRT (core dumped) +++
Aborted (core dumped)
Loading qpidd up in gdb and putting a breakpoint on lseek (what caused the
illegal seek in the system trace) gives the following backtrace:
#0 0x00000037c84f5de0 in lseek64 () from /lib64/libc.so.6
#1 0x00000037c8476775 in __GI__IO_file_seekoff () from /lib64/libc.so.6
#2 0x00000037c8478107 in __GI__IO_file_attach () from /lib64/libc.so.6
#3 0x00000037c846bd37 in fdopen@@GLIBC_2.2.5 () from /lib64/libc.so.6
#4 0x00000037c8468e88 in perror () from /lib64/libc.so.6
#5 0x0000000000668f03 in qpid::sys::Mutex::lock() ()
#6 0x0000000000668fa4 in
qpid::sys::ScopedLock<qpid::sys::Mutex>::ScopedLock(qpid::sys::Mutex&) ()
#7 0x00000000008b0048 in
qpid::sys::DeletionManager<qpid::sys::PollerHandlePrivate>::AllThreadsStatuses::~AllThreadsStatuses()
()
#8 0x00000037c8439279 in __run_exit_handlers () from /lib64/libc.so.6
#9 0x00000037c84392c5 in exit () from /lib64/libc.so.6
#10 0x00000037c8421b4c in __libc_start_main () from /lib64/libc.so.6
#11 0x0000000000648389 in _start ()
Hope it helps narrow down the issue.