This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ASSERTS & TRACING quit working
- To: "'Jonathan Larmour'" <jlarmour at redhat dot com>
- Subject: RE: [ECOS] ASSERTS & TRACING quit working
- From: "Trenton D. Adams" <tadams at extremeeng dot com>
- Date: Wed, 11 Jul 2001 16:22:39 -0600
- Cc: "'eCos discussion'" <ecos-discuss at sources dot redhat dot com>
- Organization: Extreme Engineering
>
> As I said it depends on the configuration. So look at the
> options there. That's just one of the options.
>
> > I also remember the first time I enabled Asserts and
> Tracing last time
> > I ended up getting way to much output. So, I disabled
> some option
> > somewhere, and then I only got what I wanted. What
> option might this
> > have been?
>
> Logging of function entry/exit probably.
I think you're right.
I'm starting to get really ticked off at this tracing thing. The output
is not the same as it was beofre, nor does it do any actual tracing
unless I specifically ask it to by calling CYG_TRACE_PRINT (). On top
of that, it outputs tracing information from kernel functions and stuff
that I don't want. It wasn't this hard to set it up before. I had it
running in 5 minutes, not 4 hours.
Could you list some quick steps that you would go through when setting
up tracing for a new eCos project?