PeerHood debugging development facility

Objectives

  • Threading management. Management of debug messages should be separated in threading, so that messages does not overlap each other. Debug macros are in practice used everywhere in code, so when using simple locking strategy implicit serialization of execution would happen.
  • Control of debug output by modules. Usually development focus into certain module and non related debug tracing output is nuisance for developer.

Current situation

Along the code DBG and ERR macros are used. On most files the target is defined by themselves, usually into syslog. There is not common control about debugging messages target. Syslog is not indeed suitable for development purposes.

Questions ?

  • Eclipse support for debug output ?