All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolae Mihalache <mache@abcpages.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 16:23:32 +0200	[thread overview]
Message-ID: <3F61D6E4.2050604@abcpages.com> (raw)
In-Reply-To: <20030912140542.GP14376@lug-owl.de>

Jan-Benedict Glaw wrote:

>
>Your approach won't work, but I can hint you to another. If you don't
>need the *wire states*, but only the data your application receives (or
>transmits), then this is easy. Simply use strace or a preload lib to
>intercept open, close, read and write.
>
>That way, you don't monitor the serial port itself, but the application
>using it. For me, that has always been enough:-)
>
This seems a good ideea. Probably I will not use exactly strace but 
develop something using the same library it uses.
I will still keep the cable break-out solution as an option but 
definitely I wanted to be able to monitor the data without interfering 
with the electic signaling on the cable.

Thanks a lot!
nicolae


  reply	other threads:[~2003-09-12 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 13:37 tcpdump equivalent for the serial port Nicolae Mihalache
2003-09-12 13:50 ` Mariano Moreyra
2003-09-12 14:01   ` Nicolae Mihalache
2003-09-12 14:08     ` Mariano Moreyra
2003-09-12 14:05 ` Jan-Benedict Glaw
2003-09-12 14:23   ` Nicolae Mihalache [this message]
2003-09-12 14:39     ` Jan-Benedict Glaw
2003-09-12 15:33       ` Nicolae Mihalache
2003-09-12 14:34 ` Jamie Le Tual
  -- strict thread matches above, loose matches on Subject: below --
2003-09-12 15:37 Nicolae Mihalache

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=3F61D6E4.2050604@abcpages.com \
    --to=mache@abcpages.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.