Runtime Toggled Debug Logging methods to quickly turn logging on and off for portions of GSK. These functions allow you to programmitcally set the GSK debugging flags. Usually, one sets these at runtime instead, by using the --gsk-debug=FLAGS command-line argument to your program. In any event, GSK's debugging facilities are only available if GSK itself was configured with gsk-debug support, by specifying --enable-gsk-debug to GSK's configure script. Flags which may be turned on to print debugging messages about them. @GSK_DEBUG_IO: I/O hook debugging. @GSK_DEBUG_STREAM: Read/write debugging. @GSK_DEBUG_STREAM_LISTENER: Server listener debugging. @GSK_DEBUG_STREAM_DATA: Stream debugging by dumping all the data exchanged with the stream. @GSK_DEBUG_LIFETIME: Debug object lifetime issues. @GSK_DEBUG_MAIN_LOOP: Debug main-loop behavior. @GSK_DEBUG_DNS: Debug name lookup behavior. @GSK_DEBUG_HOOK: Debug hooks. @GSK_DEBUG_SSL: Debug SSL (a secure transport layer, used by https). @GSK_DEBUG_HTTP: Debug HTTP, the protocol used for web pages. @GSK_DEBUG_FTP: @GSK_DEBUG_REQUEST: @GSK_DEBUG_FD: Debug file-descriptor usage. @GSK_DEBUG_ALL: All debug flags. Whether debugging is on. This corresponds with whether GSK's configure script was run with the --enable-gsk-debug option. @flags: @flags: