After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 620913 - More control with G_DBUS_DEBUG
More control with G_DBUS_DEBUG
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gdbus
unspecified
Other All
: Normal normal
: ---
Assigned To: David Zeuthen (not reading bugmail)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-06-07 22:30 UTC by Allison Karlitskaya (desrt)
Modified: 2010-07-01 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2010-06-07 22:30:58 UTC 
would be nice if there was some way to get a view of all of the messages going in and out, but without the hexdump
Comment 1 David Zeuthen (not reading bugmail) 2010-06-07 22:32:51 UTC 
Yep. I suggest splitting 'message' up into 'messages' and 'payload'. 

From IRC

<desrt> btw
 about the G_DBUS_DEBUG stuff...
 1) i saw some conflicting notes in the docs and code about if it should be =messages or =message
 2) it would be nice if the debug flags supported not just which events to report but also in how much default
 *detail
<davidz> desrt: file a bug about message vs. messages? (never heard about that before)
 desrt: re detail... I dunno. I don't like having both message and messages or having an option to control granularity...
<desrt> david; gdbusconnection.c line 74
  *   debug output when using G_DBUS_DEBUG=messages, e.g. in addition to
Comment 2 David Zeuthen (not reading bugmail) 2010-07-01 18:40:16 UTC 
Done, see

http://git.gnome.org/browse/glib/commit/?id=bd8d837f573a784a234740bd49f9103cdf70c268

that also addds other useful G_DBUS_DEBUG flags.