I'd like to find out what files are used by shell-commands. The purpose is for automatic dependency detection on a make-like system. One approach is to wrap the command with strace: 
use POSIX 'tmpnam';

my $cmd = "cat /dev/null";
my $trace_file = tmpnam;

system "strace -f -e trace=open -o $trace_file $cmd";

my %files = ();

open TRACE, "<$trace_file";
while (<TRACE>)
{
    /^open\("(.*)", O_/ and $files{$1}++;
}
close TRACE;
unlink $trace_file;

print join "\n", sort keys %files;

[download]
Even after a perfect cleanup, this code would leave much to be desired: it is not portable. It doesn't even work under Cygwin! Another problem is that strace can't be invoked recursively, which could be an issue with recursive makefiles. I was wondering if, hidden inside one of the various Run::* modules (or elsewhere), there is simpler, more portable, way?

Dave.

In reply to Detecting Files used by a shell command by dpuu

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.