This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Debug messages through serial communication port
- To: Cristiano Ligieri Pereira <cpereira at ics dot uci dot edu>
- Subject: Re: [ECOS] Debug messages through serial communication port
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Thu, 06 Sep 2001 21:46:04 +0100
- Cc: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>,ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <Pine.SOL.4.20.0108291026210.7218-100000@washoe.ics.uci.edu>
Cristiano Ligieri Pereira wrote:
>
> 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.
If you're using GDB, then the GDB stubs in your program will be waiting for
an ack from GDB after every line is output. This all happens with
interrupts disabled.
The cumulative effect of that may be what the problem is.
Also there is a certain amount of buffering in the diag code, in as much as
it waits for a newline, but that's all.
Jifl
> 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?
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine