• spiiroin's avatar
    [debug] Optionally include file/line/function info when logging to stderr · 7ea43c3b
    spiiroin authored
    When debugging usb-moded it is time consuming to find where the
    various debug messages originate from.
    
    When logging to stderr, prefix the messages with source code
    position info similar as gcc uses for reporting compilation
    issues. This allows browsing usb-moded code with jump to the
    next error functionality available in many text editors.
    
    Since the amount of information passed to logging functions
    is significantly increased, check whether the message would
    be emitted or not before evaluating formatting parameters etc.
    
    Also make variables relating to logging level, type, etc
    available only via accessor functions.
    Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
    7ea43c3b
Name
Last commit
Last update
config Loading commit data...
debian Loading commit data...
docs Loading commit data...
openembedded Loading commit data...
rpm Loading commit data...
src Loading commit data...
systemd Loading commit data...
utils Loading commit data...
.gitignore Loading commit data...
Copyright Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.md Loading commit data...
TODO Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
usb-moded.ini Loading commit data...
usb_moded.pc.in Loading commit data...