public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Debug messages through serial communication port
Date: Wed, 29 Aug 2001 10:31:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.20.0108291026210.7218-100000@washoe.ics.uci.edu> (raw)
In-Reply-To: <000a01c130ab$23613ac0$090110ac@TRENT>

The faster the clock tick, the worse the problem. I think i'll have to
live with that, store my debugging info on memory and dump it once and a
while.

Cristiano.

------------------------------------------------------------
Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira

On Wed, 29 Aug 2001, Trenton D. Adams wrote:

> I have the same problem.  It doesn't bother me that much so I haven't
> bothered to figure out why it's happening.
> 
> I have a series of diag_printfs with cyg_thread_delays in between.  It
> appears as if all the cyg_thread_delays are run through first, and then
> the diag_printfs.  I don't know why this would happen, but it does.  Is
> this similar to your problem?

  parent reply	other threads:[~2001-08-29 10:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28 23:06 Cristiano Ligieri Pereira
2001-08-29  6:24 ` Grant Edwards
2001-08-29  9:48   ` Cristiano Ligieri Pereira
2001-08-29  9:54 ` Trenton D. Adams
2001-08-29 10:01   ` Cristiano Ligieri Pereira
2001-08-29 10:31   ` Cristiano Ligieri Pereira [this message]
2001-09-06 13:46     ` Jonathan Larmour
2001-09-06 17:21       ` Cristiano Ligieri Pereira
2001-09-06 17:25         ` Jonathan Larmour
2001-09-07  7:19           ` Grant Edwards

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=Pine.SOL.4.20.0108291026210.7218-100000@washoe.ics.uci.edu \
    --to=cpereira@ics.uci.edu \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=tadams@theone.dnsalias.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).