Bug 34070 - Read DBus traces in libpcap format
Summary: Read DBus traces in libpcap format
Status: RESOLVED FIXED
Alias: None
Product: Bustle
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: Will Thompson
QA Contact:
URL: http://cgit.freedesktop.org/bustle/lo...
Whiteboard:
Keywords:
Depends on:
Blocks: 34105
  Show dependency treegraph
 
Reported: 2011-02-09 04:46 UTC by Martin Vidner
Modified: 2012-01-13 03:44 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Vidner 2011-02-09 04:46:30 UTC
Bustle uses a custom scraper and log format to gather the messages. Switch to a common format piloted in dbus-dump, an instance of the libpcap format used in tcpdump and Wireshark.

"""dbus-dump is a tool to capture D-Bus messages in a libpcap capture file.

It takes an idea from dbus-scrape, which processes a strace output of dbus-monitor, and takes it further by stracing dbus-daemon, thus not relying on any eavesdropping (mis)configuration.

The intended purpose is to establish the libpcap capture format as a base for debugging tools like

    * dbus-monitor
    * DBusMessageBox
    * Bustle
    * dbus-spy
"""
( from https://github.com/mvidner/dbus-dump )
Comment 1 Will Thompson 2011-06-26 04:13:53 UTC
I've got preliminary support for loading logs from pcap files in the 'pcap' branch. I also wrote a GDBus-based pcap-logging tool, akin to bustle-dbus-monitor; I think the stracing approach (or some other approach attached directly to the daemon) is probably the better one, but nonetheless thought it would be fun to write another logger. :)

Current issues:

 • Shoddy error handling;
 • Doesn't show method replies/errors.
Comment 2 Will Thompson 2012-01-13 03:44:17 UTC
This is implemented in Bustle 0.3.1.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.