From: Valdis.Kletnieks@vt.edu
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: ranjith kumar <ranjithproxy@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: how to know list of files accessed
Date: Mon, 13 Feb 2012 23:44:24 -0500 [thread overview]
Message-ID: <8249.1329194664@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 13 Feb 2012 13:32:56 +0100." <4F3902F8.3090905@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On Mon, 13 Feb 2012 13:32:56 +0100, Michael Opdenacker said:
> An easy way is to run your command with 'strace' to trap all the calls
> to 'open':
>
> strace make 2>&1 | grep open
You really want 'strace -f make' - the -f flag makes it follow forks, which you
want to do because it's gcc that's doing most of the actual file I/O, not make.
Oh. and you want to redirect that grep into a temporary file and be
prepared to post-process it with perl or something, there's going to be
*zillions* of open() syscalls.
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-02-14 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 11:30 ranjith kumar
2012-02-13 12:32 ` Michael Opdenacker
2012-02-14 4:44 ` Valdis.Kletnieks [this message]
2012-02-14 8:26 ` Matthias Schniedermeyer
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=8249.1329194664@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=ranjithproxy@gmail.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
all inboxes | Powered by JetHome®