Debugging dbus communication

[László Monda]

I assume this is what I'm looking for:

method call sender=:1.1263 -> dest=org.freedesktop.DBus serial=7
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=AddMatch
   string "type='signal',interface='ca.desrt.dconf.Writer',path='/ca/desrt/dconf/Writer/user',arg0path='/org/gnome/desktop/screensaver/'"

Correct?

Also, based on what I've read the sender is randomly-assigned client
ID that I cannot trace back.  Still, is there any way to know what
processes operate behind those IDs?

Thanks in advance!

On Mon, May 6, 2013 at 2:49 AM, Thiago Macieira <thiago at kde.org> wrote:
> On domingo, 5 de maio de 2013 22.14.48, László Monda wrote:
>> On Sun, May 5, 2013 at 5:26 PM, Thiago Macieira <thiago at kde.org> wrote:
>> > On domingo, 5 de maio de 2013 11.44.38, László Monda wrote:
>> >> Basically I'd like to be able to list the subscribers of such
>> >> messages.  How is this possible?
>> >
>> > It's not possible to list them.
>> >
>> > To get the list, you need to start monitoring the AddRule call from the
>> > very beginning (before any rules you're interested in are added).
>>
>> Could you please give me some context regarding the AddRule call?
>> Like is it part of the dbus source code in which case should I pull
>> the source, insert a debug line and build it?
>
> No, use dbus-monitor from very early on. Catch and log every AddRule call.
>
> If you know all the AddRules, all the RemoveRules and all the clients that
> disconnected, you know who is subscribed.
>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>    Software Architect - Intel Open Source Technology Center
>       PGP/GPG: 0x6EF45358; fingerprint:
>       E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus
>



-- 
László Monda <http://monda.hu>