From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: "'eCos discussion'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] ASSERTS & TRACING quit working
Date: Wed, 11 Jul 2001 14:53:00 -0000 [thread overview]
Message-ID: <000101c10a53$f3aed850$090110ac@TRENT> (raw)
In-Reply-To: <3B4CC755.C7E47434@redhat.com>
>
> And you enabled the individual option underneath that?
>
Yes.
> > I've enabled Asserts & Tracing just the way I did before.
> The only
> > problem is this time it's not working.
> >
> > Also, I don't actually need to call CYG_TRACE_PRINT ()
> whenever I want
> > it to output what I've traced so far right? If so, how
> come I didn't
> > need to do this before?
>
> 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.
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?
next prev parent reply other threads:[~2001-07-11 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 9:27 Trenton D. Adams
2001-07-11 14:27 ` Jonathan Larmour
2001-07-11 14:34 ` Trenton D. Adams
2001-07-11 14:38 ` Jonathan Larmour
2001-07-11 14:53 ` Trenton D. Adams [this message]
2001-07-11 15:00 ` Jonathan Larmour
2001-07-11 15:22 ` Trenton D. Adams
2001-07-11 15:25 ` Jonathan Larmour
2001-07-12 8:27 ` Trenton D. Adams
2001-07-12 8:47 ` Jonathan Larmour
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='000101c10a53$f3aed850$090110ac@TRENT' \
--to=tadams@extremeeng.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).