linux-c-programming.vger.kernel.org archive mirror
 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 17:33:52 +0200	[thread overview]
Message-ID: <3F61E760.3070304@abcpages.com> (raw)
In-Reply-To: <20030912143927.GS14376@lug-owl.de>

Jan-Benedict Glaw wrote:

>On Fri, 2003-09-12 16:23:32 +0200, Nicolae Mihalache <mache@abcpages.com>
>wrote in message <3F61D6E4.2050604@abcpages.com>:
>  
>
>>Jan-Benedict Glaw wrote:
>>    
>>
>>>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.
>>    
>>
>
>  
>
Hello again,

Now that I'm thinking better, this approach is not similar with tcpdump 
because if I monitor the application that reads the data, I won't see it 
until it is actualy read. The idea of my sniffer is to debug the device 
that runs on the other side so it would be interesting to display 
something as soon as it arrives rather than waiting till the application 
reads the data.
I will try to see if there is some support provided in the kernel.

Thanks,
nicolae


  reply	other threads:[~2003-09-12 15:33 UTC|newest]

Thread overview: 9+ 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
2003-09-12 14:39     ` Jan-Benedict Glaw
2003-09-12 15:33       ` Nicolae Mihalache [this message]
2003-09-12 14:34 ` Jamie Le Tual

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=3F61E760.3070304@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 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 NNTP newsgroup(s).