public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>,
	ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Debug messages through serial communication port
Date: Fri, 07 Sep 2001 07:19:00 -0000	[thread overview]
Message-ID: <20010907092202.A8439@visi.com> (raw)
In-Reply-To: <3B98143C.E42A855E@redhat.com>

On Fri, Sep 07, 2001 at 01:26:36AM +0100, Jonathan Larmour wrote:
> Cristiano Ligieri Pereira wrote:
> > 
> > Therefore I cannot get away from this "problem"?
> 
> On a production system you won't have GDB on the other end, and there won't
> be any delays. But to use GDB, that's the rules we have to play with I'm
> afraid.
> 
> Although... if have a second port, you could configure eCos to send the
> diag output out that instead.

That's what I do.  I've got two "extra" serial ports.
diag_printf() output goes to one, and gdb uses the other.  It
works very nicely that way.  Well, I do have some things I need
to fix to get gdb to work right, but that's another thread.

-- 
Grant Edwards
grante@visi.com

      reply	other threads:[~2001-09-07  7:19 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
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 [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=20010907092202.A8439@visi.com \
    --to=grante@visi.com \
    --cc=cpereira@ics.uci.edu \
    --cc=ecos-discuss@sourceware.cygnus.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).