This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ASSERTS & TRACING quit working
- To: "Trenton D. Adams" <tadams at extremeeng dot com>
- Subject: Re: [ECOS] ASSERTS & TRACING quit working
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Wed, 11 Jul 2001 23:00:25 +0100
- Cc: 'eCos discussion' <ecos-discuss at sources dot redhat dot com>
- Organization: Red Hat UK Ltd.
- References: <000101c10a53$f3aed850$090110ac@TRENT>
"Trenton D. Adams" wrote:
> >
> > Depends on the configuration of the tracing system, for
> > example with buffered tracing but
> > CYGDBG_INFRA_DEBUG_TRACE_BUFFER_PRINT disabled (which it is
> > by default) you won't see anything unless you explicitly ask for it.
> >
>
> But I want tracing to occur every single time, not just when the buffer
> is full. Can I do that? It seemed to me before that that's exactly
> what it was doing.
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.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/