1. 17 Aug, 2017 1 commit
    • spiiroin's avatar
      [debug] Optionally include file/line/function info when logging to stderr · 3420f50a
      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>
      3420f50a
  2. 05 May, 2017 2 commits
  3. 26 Apr, 2017 11 commits
  4. 24 Mar, 2017 7 commits
  5. 13 Mar, 2017 4 commits
  6. 06 Mar, 2017 1 commit
  7. 14 Feb, 2017 6 commits
  8. 31 Jan, 2017 3 commits
  9. 07 Dec, 2016 5 commits