From: Torfinn Ingolfsen on
On Thu, Mar 18, 2010 at 10:16 PM, Adam Vande More <amvandemore(a)gmail.com>wrote:

> On Thu, Mar 18, 2010 at 4:12 PM, Torfinn Ingolfsen <tingox(a)gmail.com>wrote:
>
>>
>>
>> Well, it says:
>> process 36926: arguments to dbus_message_new_signal() were incorrect,
>> assertion
>> "_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.
>>
>
> Did you restart dbus after that?
>

Yes, I did. But I understand the question. :-)

--
Regards,
Torfinn Ingolfsen
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Garrett Cooper on
On Thu, Mar 18, 2010 at 2:15 PM, Torfinn Ingolfsen <tingox(a)gmail.com> wrote:
> Hi,
>
> On Thu, Mar 18, 2010 at 8:04 PM, Gary Jennejohn <gary.jennejohn(a)freenet.de>
> wrote:
>>
>> [snip the rest]
>>
>> Do you have any strange malloc(3) flags set?
>>
> Not that I know of.
> root(a)kg-v7# more /etc/src.conf
> /etc/src.conf: No such file or directory
> root(a)kg-v7# more /etc/make.conf
> # added by use.perl 2010-03-12 20:15:36
> PERL_VERSION=5.10.1

I think Gary meant, is /etc/malloc.conf set to anything?
Thanks,
-Garrett
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Garrett Cooper on
On Thu, Mar 18, 2010 at 7:03 PM, Garrett Cooper <yanefbsd(a)gmail.com> wrote:
> On Thu, Mar 18, 2010 at 2:15 PM, Torfinn Ingolfsen <tingox(a)gmail.com> wrote:
>> Hi,
>>
>> On Thu, Mar 18, 2010 at 8:04 PM, Gary Jennejohn <gary.jennejohn(a)freenet.de>
>> wrote:
>>>
>>> [snip the rest]
>>>
>>> Do you have any strange malloc(3) flags set?
>>>
>> Not that I know of.
>> root(a)kg-v7# more /etc/src.conf
>> /etc/src.conf: No such file or directory
>> root(a)kg-v7# more /etc/make.conf
>> # added by use.perl 2010-03-12 20:15:36
>> PERL_VERSION=5.10.1
>
>    I think Gary meant, is /etc/malloc.conf set to anything?

i.e...

[gcooper@ ~]$ ls -l /etc/malloc.conf
lrwxr-xr-x 1 root wheel 1 Jan 1 2009 /etc/malloc.conf -> j
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Torfinn Ingolfsen on
On Fri, Mar 19, 2010 at 3:03 AM, Garrett Cooper <yanefbsd(a)gmail.com> wrote:

> On Thu, Mar 18, 2010 at 2:15 PM, Torfinn Ingolfsen <tingox(a)gmail.com>
> wrote:
> > Hi,
> >
> > On Thu, Mar 18, 2010 at 8:04 PM, Gary Jennejohn <
> gary.jennejohn(a)freenet.de>
> > wrote:
> >>
> >> [snip the rest]
> >>
> >> Do you have any strange malloc(3) flags set?
> >>
> > Not that I know of.
> > root(a)kg-v7# more /etc/src.conf
> > /etc/src.conf: No such file or directory
> > root(a)kg-v7# more /etc/make.conf
> > # added by use.perl 2010-03-12 20:15:36
> > PERL_VERSION=5.10.1
>
> I think Gary meant, is /etc/malloc.conf set to anything?
>

Aha! I didn't know about that one.
No, it isn't set:
root(a)kg-v7# ls -l /etc/malloc.conf
ls: /etc/malloc.conf: No such file or directory
root(a)kg-v7# env | grep MALLOC
root(a)kg-v7#

HTH
--
Regards,
Torfinn Ingolfsen
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Gary Jennejohn on
On Thu, 18 Mar 2010 22:20:23 +0100
Torfinn Ingolfsen <tingox(a)gmail.com> wrote:

> On Thu, Mar 18, 2010 at 10:16 PM, Adam Vande More <amvandemore(a)gmail.com>wrote:
>
> > On Thu, Mar 18, 2010 at 4:12 PM, Torfinn Ingolfsen <tingox(a)gmail.com>wrote:
> >
> >>
> >>
> >> Well, it says:
> >> process 36926: arguments to dbus_message_new_signal() were incorrect,
> >> assertion
> >> "_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.
> >>
> >
> > Did you restart dbus after that?
> >
>
> Yes, I did. But I understand the question. :-)
>

[I trimmed Cc]

Looking at dbus-memory.c it checks whether DBUS_MALLOC_BACKTRACES is set
in its environment. If it is, it will try to do a backtrace.

Unfortunately, the pre-requisites for actually doing the backtrace
aren't met with FreeBSD (HAVE_BACKTRACE and DBUS_BUILT_R_DYNAMIC
defined in config.h) so it won't work anyway.

It is possible to turn off all checking by defining DBUS_DISABLE_CHECKS
in config.h _before_ compiling dbus, but that may be a bad idea.

Anyway, there's alreay /* #undef DBUS_DISABLE_CHECKS */ in config.h
so you could theoretically try this out:

a) make configure
b) edit work/dbus-1.2.16/config.h and #define DBUS_DISABLE_CHECKS there
c) reinstall dbus
d) see what happens

No guarantees and use at you own risk, etc.

---
Gary Jennejohn
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"