Fri 7 Dec 2007
I’ve been playing around with a little tool for debugging applications on the bus. It is far from done but I decided to release it now that it has become useful. Right now you can see all names on the Session and System buses and get information on the objects and interfaces they export.
Current Features
- View names on the session and system bus
- View exported objects, interfaces, methods and signals
- View the full command line of services on the bus
- Execute methods with parameters on the bus and see their return values
Planed Features
- Attach to any address
- Watch, edit and play back method calls
- Watch signals
- Attach scripted actions to triggers
- Profiler for D-Bus calls
- Assistant for creating async call chains
Info
Homepage: http://hosted.fedoraproject.org/projects/d-feet/
Tarball: http://johnp.fedorapeople.org/d-feet-0.1.4.tar.gz
Fedora: yum install d-feet
(Should be built for Rawhide, F-8 and F-7 though it may take a bit to be pushed as an update to F-8 and F-7)
December 7th, 2007 at 5:02 pm
I take it that you are aware of dbus-inspector (also pygtk).
http://www.vitavonni.de/projekte/dbus-inspector.html.en
http://svn.gnome.org/viewvc/dbus-inspector/
I have used it with good success
December 7th, 2007 at 5:30 pm
Nice
Do you know http://svn.gnome.org/viewvc/dbus-inspector/trunk/ from http://www.vitavonni.de/projekte/dbus-inspector.html.en ?
December 7th, 2007 at 6:06 pm
> View names on the session and system bus
> View exported objects, interfaces, methods and signals
> Execute methods with parameters on the bus and see their return values
All this is already available in qdbusviewer in qt4-devel and has been for months.
The “full command line” is a nice feature though and the planned features are even nicer.
December 7th, 2007 at 6:29 pm
The project was twofold to get me back into Gtk+ development and to really take my knowledge of D-Bus’s internals into an all encompassing tool. I work primarily with python and Gtk+ so while there may be a good Qt tool it doesn’t really interest me though I think we can learn something from each other.
As for dbus-inspector I completely knew about that codebase and looked at it briefly but came to the conclusion that the internals weren’t attacking D-Bus from quite the right direction.
That being said, this is just one of my pet projects to keep me sane and competition is welcome
December 7th, 2007 at 8:03 pm
You do realise that your tarball link is pointing at a screenshot?
December 7th, 2007 at 8:11 pm
Thanks, fixed
December 7th, 2007 at 8:15 pm
Ah-ehm. What about dbus 1.2.0?
December 7th, 2007 at 8:17 pm
Gentoo: http://bugs.gentoo.org/show_bug.cgi?id=201639
December 7th, 2007 at 9:34 pm
Sorry for being OT but I really like the logo. Was it made with the Gimp and if so how? Thanks!
December 8th, 2007 at 2:33 am
Pieter,
Not OT at all. You have Nicu Buculei of the Fedora Art team to thank for the logo. It is done in inkscape as an svg and converted down to png for the web. Here is the end of that thread which contains the svg sources:
https://www.redhat.com/archives/fedora-art-list/2007-December/msg00030.html
December 8th, 2007 at 4:40 am
Let me suggest to you, as an improvement over dbus-viewer, qdbus, kdbus and their ilk, to be able to add more buses other than system & session. Once you implement that, I’m going to show you something cool with it
December 16th, 2007 at 12:26 pm
greatings…
agree…