I'm having a bit of trouble understanding how to use the trace facilities. I have configured my system with CYGDBG_USE_TRACING enabled (and I also have CYGDBG_USE_ASSERTS enabled), and I am getting a lot of messages generated from the kernel. For example:
TRACE: clock.cxx [ 706] void Cyg_Alarm::initialize() TRACE: clock.cxx [ 285] void Cyg_Counter::add_alarm() TRACE: clock.cxx [ 285] void Cyg_Counter::add_alarm() TRACE: clock.cxx [ 706] void Cyg_Alarm::initialize() TRACE: thread.cxx [ 337] static void Cyg_Thread::sleep() TRACE: mlqueue.cxx [ 276] void Cyg_Scheduler_Implementation::rem_thread() TRACE: mlqueue.cxx [ 276] void Cyg_Scheduler_Implementation::rem_thread() TRACE: mlqueue.cxx [ 330] void Cyg_Scheduler_Implementation::rem_thread() TRACE: thread.cxx [ 358] static void Cyg_Thread::sleep() TRACE: mlqueue.cxx [ 748] void Cyg_ThreadQueue_Implementation::enqueue() TRACE: mlqueue.cxx [ 748] void Cyg_ThreadQueue_Implementation::enqueue() TRACE: mlqueue.cxx [ 825] void Cyg_ThreadQueue_Implementation::enqueue() TRACE: mlqueue.cxx [ 119] Cyg_Thread* Cyg_Scheduler_Implementation::schedule() What is the recommended way of turning all of these off and restricting the tracing to the code I explicitly want enabled? Thanks, Rob. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
