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: Thu, 12 Jul 2001 16:47:27 +0100
- Cc: 'eCos discussion' <ecos-discuss at sources dot redhat dot com>
- Organization: Red Hat UK Ltd.
- References: <000101c10ae7$3a3a7fc0$090110ac@TRENT>
"Trenton D. Adams" wrote:
> > Then enable CYGDBG_INFRA_DEBUG_TRACE_BUFFER_PRINT. Or don't
> > use buffered tracing at all, but fancy tracing
> > (CYGDBG_INFRA_DEBUG_TRACE_ASSERT_FANCY)
> > instead.
>
> Thanks. That must be what I did before. I enabled simple output and
> disabled buffered tracing. The two are mutually exclusive though.
> Maybe the eCos configuration should make it so one can't be selected
> unless the other one is unselected? Is there a mechanism for this in
> the ecos configuration? eCos compiles fine if both are selected, but an
> eCos application will not link with eCos. It says something about some
> variuos trace functions being duplicated. I would post the output, but
> I don't want to have to recompile again because it takes a very long
> time.
It's easily fixed, and I've done so internally.
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/