Re: [ECOS] Trace Disable

[Jonathan Larmour <jifl at eCosCentric dot com>]

sensitron medical wrote:
> Is there a way to disable tracing at run-time? I see
> in the documentation that I can use BOOLs to disable
> my own CYG_TRACE calls, but that doesn't stop the
> kernel-instrumented traces that I have enabled. What I
> ended up doing was writing two methods,
> cyg_traceenable and cyg_tracedisable that simply set
> cyg_infra_trace_buffer_enable true or false.

Tweaking cyg_infra_trace_buffer_enable is exactly the intended route.

> It seems like a useful debugging technique if you are
> tracing to a circular buffer would be to freeze the
> trace buffer after a particular event so that you can
> see what happen just prior to the event. If you don't
> disable, the buffer will fill and overwrite the good
> stuff with new data before you have a chance to
> examine it.

Sure, although note that one of the main reasons for 
cyg_infra_trace_buffer_enable is so that it's easy to set in GDB, rather 
than programmatically.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss