From: "Rob Duncan" <rob.duncan@designmagnitude.com>
To: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How to use the trace facilities
Date: Tue, 17 Apr 2007 15:46:00 -0000 [thread overview]
Message-ID: <be72a610704170845ge3fa607of4f0cb6d2fec5019@mail.gmail.com> (raw)
In-Reply-To: <20070417061252.GM5526@lunn.ch>
Thanks for the reply, Andrew. It seems that the trace messages that
are causing me problems are not conditionally enabled. For example,
the ones in clock.cxx and mlqueue.cxx are generated with
CYG_REPORT_FUNCTION(), which is unconditionally enabled when I
configure with CYGDBG_USE_TRACING. And it appears that I can't
locally override that configuration option in those compilation units
because cyg_trac.h includes pkgconf/infra.h directly (where it is
defined).
I feel like I'm missing something obvious...
Rob.
On 4/16/07, Andrew Lunn <andrew@lunn.ch> wrote:
> On Mon, Apr 16, 2007 at 05:18:11PM -0700, Rob Duncan wrote:
> > I'm having a bit of trouble understanding how to use the trace
> > facilities. I have configured my system with CYGDBG_USE_TRACING
> > enabled (and I also have CYGDBG_USE_ASSERTS enabled), and I am getting
> > a lot of messages generated from the kernel. For example:
> >
...
> > TRACE: clock.cxx [ 706] void Cyg_Alarm::initialize()
> > TRACE: mlqueue.cxx [ 276] void Cyg_Scheduler_Implementation::rem_thread()
...
> > What is the recommended way of turning all of these off and
> > restricting the tracing to the code I explicitly want enabled?
>
> There are lots of comments in the header file
> packages/infra/current/include/cyg_trace.h.
>
> Basically you need to turn it on/off per compilation unit using
> #defines.
>
> Andrew
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-04-17 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 0:18 Rob Duncan
2007-04-17 6:13 ` Andrew Lunn
2007-04-17 15:46 ` Rob Duncan [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=be72a610704170845ge3fa607of4f0cb6d2fec5019@mail.gmail.com \
--to=rob.duncan@designmagnitude.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).