DebugController
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::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.
Since
2.72
Inheritors
Types
The DebugControllerImpl type represents a native instance of the DebugController interface.
Properties
Functions
Given @connection to communicate with a proxy (eg, a #GSocketConnection that is connected to the proxy server), this does the necessary handshake to connect to @proxy_address, and if required, wraps the #GIOStream to handle proxy payload.
Asynchronous version of g_proxy_connect().
See g_proxy_connect().
Get the value of #GDebugController:debug-enabled.
Initializes the object implementing the interface.
Set the value of #GDebugController:debug-enabled.
Some proxy protocols expect to be passed a hostname, which they will resolve to an IP address themselves. Others, like SOCKS4, do not allow this. This function will return false if @proxy is implementing such a protocol. When false is returned, the caller should resolve the destination hostname first, and then pass a #GProxyAddress containing the stringified IP address to g_proxy_connect() or g_proxy_connect_async().