use the log features of the GLib to have verbose output of the capturing engine,...
authorUlf Lamping <ulf.lamping@web.de>
Thu, 26 May 2005 17:50:27 +0000 (17:50 -0000)
committerUlf Lamping <ulf.lamping@web.de>
Thu, 26 May 2005 17:50:27 +0000 (17:50 -0000)
commit5d404864f204147ede0cb6e19c64e06ebdb85496
tree91a8bae1bf7b20b378e960da7c100cb4475479ef
parent4a5deae5759f85eba4592689aec83ce380959af6
use the log features of the GLib to have verbose output of the capturing engine, e.g. GLib provides different domains for different submodules. Output more verbose than warning level will be disabled by default (just like before).

use the console_log_handler in main.c for win32 AND unix now

Currently use the log for the capturing engine (only), as I desperately needed a log output for debugging.

svn path=/trunk/; revision=14438
capture.c
capture.h
capture_loop.c
capture_opts.c
capture_sync.c
gtk/main.c
log.h [new file with mode: 0644]