assertion failure in D-bus code

Ethan Blanton elb at
Tue May 8 16:52:02 EDT 2007

Oleg Sukhodolsky spake unto us the following wisdom:
> On 5/8/07, Ethan Blanton <elb at> wrote:
> > Richard Laager spake unto us the following wisdom:
> > > > That assertion is probably unrelated to the core dump.
> > >
> > > It's directly related. He's running with --enable-fatal-asserts, so that
> > > assertion failure will cause an abort().
> >
> > Yeah, I saw that in your reply email ... it never occurred to me that
> > someone would go out of their way to compile with --enable-bustination
> > and then ask why things were bustinated.  Live and learn.
> I'm not asking why pidgin exits after assertion, I'm asking why the
> assertion fails.

The assertion fails *hard* because you compiled with
--enable-fatal-asserts. Had you not done that, it would have simply
printed a harmless message and continued.  The assertion failure
itself is because an argument to some signal is of an object which is
not registered with the D-Bus interface.


The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <>

More information about the Devel mailing list