Re: dbus-trace

Zeeshan Ali Khan <[email protected]> Fri, 18 Nov 2022 23:44:57 +0100
Newsgroups gmane.comp.freedesktop.dbus
Message-ID <CAAa3hFN-O=+pD-2ZMBO8xk9Xu9TQpwp16bE46NOrxHh1Ek-PQw@mail.gmail.com>
Hi Thomas,

This seems like a super useful tool. Thanks for writing it. 👍

On Fri, 18 Nov 2022 at 17:38, Thomas Kluyver <[email protected]> wrote:

> Hi all,
>
> I've just released a tiny tool called dbus-trace, which can inspect what
> D-Bus messages a program sends and receives.
>
> https://gitlab.com/takluyver/dbus-trace
>
> The difference from things like dbus-monitor and Bustle is that it sits
> between a child process and the real bus, passing messages through. This
> makes it easy to focus on what a single program is doing (no need to figure
> out its D-Bus unique name), and also means you can see D-Bus messages that
> are rejected by a proxy (e.g. in a Flatpak sandbox) before they get to the
> real bus.
>
> This is very minimal at the moment - there are obvious extensions e.g.
> filtering which messages are shown, or writing to a file, which could be
> added if it proves useful. But it helped me figure out a real-world issue
> today, so I thought it was time to write a README and call it 0.1.
>
> Have a good weekend,
> Thomas Kluyver
>


-- 
Regards,

Zeeshan Ali Khan