From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bart Veer <bartv@redhat.com>
To: colin.ford@pipinghotnetworks.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Debug and Tracing?
Date: Tue, 12 Sep 2000 09:44:00 -0000
Message-id: <200009121644.RAA16465@sheesh.cygnus.co.uk>
References: <39BE57A0.6946F73@pipinghotnetworks.com>
X-SW-Source: 2000-09/msg00164.html

>>>>> "Colin" == Colin Ford <colin.ford@pipinghotnetworks.com> writes:

    Colin> I must be really thick but I can't find out how to get
    Colin> the tracing working? What do I have to set and can
    Colin> I do it using ecosconfig ?

It can be done by manually editing the ecos.ecc savefile used by
ecosconfig. Details of this process can be found in the User's Guide,
the Manual Configuration section goes into some detail about the
savefile format and how to modify it.

Tracing is controlled by the CYGDBG_USE_TRACING option of the
infrastructure package. First you need to enable debugging generally,
i.e. CYGPKG_INFRA_DEBUG, which will provide some generic support.
Enabling debugging automatically switches on assertions
(CYGDBG_USE_ASSERTS) which you can disable - although I would advise
against that unless you are running into code size problems. It will
not give you tracing automatically because generally that is too
expensive, but you can enable tracing explicitly by changing the value
of CYGDBG_USE_TRACING.

In addition you need to decide what should happen to the events being
traced and how much information should be collected. There is more
information about this in the User's Guide, the section on
Debugging Techniques.

Bart Veer // eCos net maintainer