DebugController

Object Hierarchy:

GLib.DebugController GLib.DebugController GLib.DebugController GLib.Object GLib.Object GLib.Object->GLib.DebugController GLib.Initable GLib.Initable GLib.Initable->GLib.DebugController

Description:

[ CCode ( type_cname = "GDebugControllerInterface" , type_id = "g_debug_controller_get_type ()" ) ]
[ Version ( since = "2.72" ) ]
public interface DebugController : Object, Initable

`GDebugController` is an interface to expose control of debugging features and debug output.

It is implemented on Linux using [class@Gio.DebugControllerDBus], which exposes a D-Bus interface to allow authenticated peers to control debug features in this process.

Whether debug output is enabled is exposed as [property@Gio.DebugController:debug-enabled]. This controls [func@GLib.log_set_debug_enabled] by default. Application code may connect to the [signal@GObject.Object:GDebugController:notify] signal for it to control other parts of its debug infrastructure as necessary.

If your application or service is using the default GLib log writer function, creating one of the built-in implementations of `GDebugController` should be all that’s needed to dynamically enable or disable debug output.

All known implementing classes:

Namespace: GLib
Package: gio-2.0

Content:

Properties:

  • public abstract bool debug_enabled { get; set; }
    true if debug output should be exposed ( for example by forwarding it to the journal), false otherwise.

Methods:

Inherited Members:

All known members inherited from class GLib.Object
All known members inherited from interface GLib.Initable