[Call for Testing] X.org 7.5 for FreeBSD
tingox at gmail.com
Thu Mar 18 21:12:24 UTC 2010
On Thu, Mar 18, 2010 at 7:53 PM, Garrett Cooper <yanefbsd at gmail.com> wrote:
> Here's the problem area that needs inspecting:
> #2 0x0000000804171c75 in dbus_malloc () from /usr/local/lib/libdbus-1.so.3
> 1. make -C $PORTSDIR/*/dbus extract
> 2. Find the file where dbus_malloc is defined.
It's in work/dbus-1.2.16/dbus/dbus-memory.c
3. Look for an abort.
There isn't one in that file as far as I can tell:
root at kg-v7# pwd
root at kg-v7# grep abort work/dbus-1.2.16/dbus/dbus-memory.c
> But in the meantime, your console may have some helpful messages worth
> looking at.
Well, it says:
process 36926: arguments to dbus_message_new_signal() were incorrect,
"_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1165.
This is normally a bug in some application using the D-Bus library.
D-Bus is not compiled with backtrace support so unable to print a backtrace
I don't know if that message is a red herring or not.
I recompiled dbus with:
make -DWITH_DEBUG all deinstall reinstall
But that didn't help a bit.
More information about the freebsd-ports