bug#13516: tests/rm/unread3 fails on Mac OS X 10.8

[Assaf Gordon]

Paul Eggert wrote, On 01/22/2013 02:01 AM:
> Thanks, to help debug that can you please try the following
> shell commands?  The idea is to run the newly-built "rm" in
> a directory that is not readable.
> 
> cd coreutils-8.20/src
> D=$(pwd)
> mkdir -p a/1 b c d/2 e/3
> cd c
> chmod u=x,go= .
> ktrace -o /tmp/tr $D/rm -r $D/a $D/b
> kdump /tmp/tr
> 
> The "ktrace" should get a trace of the system calls executed
> by the failing "rm", and the "kdump" should generate a printable
> output of that.

ktrace/kdump are not available any more on Mac OS X (since 10.5).
I found "dtruss" - but got into a catch-22:

1. Running 'rm' as-is gives error:
    $ $D/rm -r $D/a $D/b                     
    /Users/admin/Projects/coreutils-8.20.90-e27bfd/src/rm: unable to record 
current working directory: Too many open files

2. Running with 'dtruss' requires root:
    $ dtruss $D/rm -r $D/a $D/b 
    dtrace: failed to initialize dtrace: DTrace requires additional privileges

3. Running with 'sudo', 'rm' doesn't fail:
    $ sudo dtruss $D/rm -r $D/a $D/b 2>/tmp/rm_trace.txt
    [ $D/a and $D/b are deleted ]

Attached is the "rm_trace.txt" file, but it won't show failure...

I'm not familiar with MacOS, so any suggestions are welcomed.


Pádraig:
running "make check" in gnulib-test directory failed 8 tests (attached).
I can try instrumentations and other tests, but please tell me how to run them.



-gordon

rm_trace.txt
Description: Text document

gnulib-test-suite.log
Description: Text Data