public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <200009121644.RAA16465@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <39BE57A0.6946F73@pipinghotnetworks.com>

>>>>> "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

      reply	other threads:[~2000-09-12  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-12  9:16 Colin Ford
2000-09-12  9:44 ` Bart Veer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200009121644.RAA16465@sheesh.cygnus.co.uk \
    --to=bartv@redhat.com \
    --cc=colin.ford@pipinghotnetworks.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).