From: Jesper Skov <jskov@redhat.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: Rafael RodrÃÂguez Velilla <rrv@tid.es>,
ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Serial spy
Date: Mon, 19 Feb 2001 23:27:00 -0000 [thread overview]
Message-ID: <otitm5g6g3.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <XFMail.20010219140319.gthomas@cambridge.redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
>>>>> "Gary" == Gary Thomas <gthomas@cambridge.redhat.com> writes:
Gary> On 19-Feb-2001 Rafael RodrÃguez Velilla wrote:
>> Has anyone got a program to spy the serial device transparently in
>> order to see the dialog of GDB and my target's stub. I just want to
>> see what's traveling along my serial conecction.
>>
Gary> You can get this information from GDB itself. (gdb) set
Gary> remotedebug 1
Unfortunately that doesn't always work. Any non-protocol data gets
binned by some GDBs - it's not consistent in this regard across
architectures.
Instead I suggest using the ser_filter for which sources are available
from the CVS repository in the host directory. You should be able to
rebuild it for Linux by invoking make in the host/tools/ecostest/unix
directory. For Windows I believe there are some MSVC build files
somewhere.
When you have ser_filter built you can do something like:
$ ser_filter -m 9999 /dev/ttyS0 38400
And then connect to the target like this:
(gdb) ta re localhost:9999
When you do, the ser_filter should dump all the traffic out on the
console.
Jesper
next prev parent reply other threads:[~2001-02-19 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 12:25 Rafael RodrÃguez Velilla
2001-02-19 13:03 ` Gary Thomas
2001-02-19 23:27 ` Jesper Skov [this message]
2001-02-21 1:59 ` Rafael RodrÃguez Velilla
2001-02-21 2:17 ` Jesper Skov
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=otitm5g6g3.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gthomas@cambridge.redhat.com \
--cc=rrv@tid.es \
/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).