How to enable Tracebacks?

Simon McVittie simon.mcvittie at
Wed Jan 17 18:26:57 PST 2007

Hash: SHA1

On Thu, 18 Jan 2007 at 12:33:17 +1100, Curtis Maloney wrote:
> I'm using dbus-1.0.2, dbus-glib-0.72 and dbus-python-0.79.93 ( 0.80rc3), 
> built on Solaris 10.
> I keep getting assertions on my app, and this message following:
> >process 8267: arguments to dbus_pending_call_set_notify() were incorrect, 
> >assertion "pending != NULL" failed in file dbus-pending-call.c line 598.
> >This is normally a bug in some application using the D-Bus library.
> >  D-Bus not compiled with backtrace support so unable to print a backtrace

You can get a core dump from this by exporting DBUS_FATAL_WARNINGS=1
when you run your app, and enabling core dumps in the usual way
(e.g. ulimit -c unlimited on Linux, I don't know whether this is necessary/the
same on Solaris) - if you could do so and get a backtrace with a
debugger, that would be very helpful.

If you could run the test suite (make check) with fatal warnings and
core dumps enabled, that would also be useful (I haven't tried it on
Solaris, although hopefully it does work).

I don't think I've fixed anything related to pending calls recently, but if
you want to give it a try you can get the current bleeding edge version from:

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: or


More information about the dbus mailing list