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 15:22:00 -0000 [thread overview]
Message-ID: <000201c10a57$ff3aa330$090110ac@TRENT> (raw)
In-Reply-To: <3B4CCC79.903FC2B0@redhat.com>
>
> As I said it depends on the configuration. So look at the
> options there. That's just one of the options.
>
> > 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?
>
> Logging of function entry/exit probably.
I think you're right.
I'm starting to get really ticked off at this tracing thing. The output
is not the same as it was beofre, nor does it do any actual tracing
unless I specifically ask it to by calling CYG_TRACE_PRINT (). On top
of that, it outputs tracing information from kernel functions and stuff
that I don't want. It wasn't this hard to set it up before. I had it
running in 5 minutes, not 4 hours.
Could you list some quick steps that you would go through when setting
up tracing for a new eCos project?
next prev parent reply other threads:[~2001-07-11 15:22 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
2001-07-11 15:00 ` Jonathan Larmour
2001-07-11 15:22 ` Trenton D. Adams [this message]
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='000201c10a57$ff3aa330$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).