From: Rechberger Markus <mrechberger@gmail.com>
To: Fabio Miranda Hamburger <fabmirha@ns.isi.ulatina.ac.cr>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: strace write/read output
Date: Wed, 23 Mar 2005 18:34:57 +0100 [thread overview]
Message-ID: <d9def9db0503230934238c870@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503221215250.31636@ns.isi.ulatina.ac.cr>
hey,
here two small examples the first one will attach strace to a running
process, the second one will fire up your application attached to
strace.
strace -e 'read,write' -p <processid> or
strace -e 'read,write' <yourapplication>
Markus
On Tue, 22 Mar 2005 12:16:55 -0600 (CST), Fabio Miranda Hamburger
<fabmirha@ns.isi.ulatina.ac.cr> wrote:
> > On Tuesday 22 March 2005 11:05 am, Fabio Miranda Hamburger wrote:
> > > hello,
> > >
> > > I am debugging a tcpip app on linux, I would like to use strace to show me
> > > *all* the data passed to read() and write() function to the sockets
> > > stream.
> > >
> > > thanks,
> > >
> > Does strace with the -e option do what you want? man strace. It seems to
> > do read and write. Prepare for big logfiles ;)
>
> I was trying to figure out how to do it. Can you provide an example?
> Usually strace shows few characters and at the end, the total length of
> what was received. Well, I need the entire string of characters.
>
> Thanks.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-03-23 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 17:05 strace write/read output Fabio Miranda Hamburger
2005-03-22 19:05 ` Eric Bambach
2005-03-22 18:16 ` Fabio Miranda Hamburger
2005-03-23 2:17 ` Eric Bambach
2005-03-23 17:34 ` Rechberger Markus [this message]
2005-04-04 14:32 ` Array Empty Slots Chris
2005-04-05 8:39 ` M.Baris Demiray
2005-04-05 9:06 ` Chris
2005-04-05 15:03 ` M.Baris Demiray
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=d9def9db0503230934238c870@mail.gmail.com \
--to=mrechberger@gmail.com \
--cc=fabmirha@ns.isi.ulatina.ac.cr \
--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).