Re: rcs configure hang

[Kelly Wang (kellythw)]

Hi Paul,

You are right, after remove confdir3, rerun strace hang.
Checked tr output, it stopped at bunch of mkdir and chdir and no further steps 
after that.
mkdir("confdir3", 0700)                 = 0
chdir("confdir3")                       = 0

Thanks,
Kelly
 
If you need support for DevX Tools:   http://devxsupport.cisco.com/
Specifically, for NXOS, see -
https://wiki.cisco.com/display/NEXUSPMO/ContactingNexusOpsAndTools
 

On 10/26/20, 3:56 PM, "Paul Eggert" <eggert@cs.ucla.edu> wrote:

    On 10/26/20 9:13 AM, Kelly Wang (kellythw) wrote:

    > [Kelly] strace step is not hang and I have tr generated.

    Looking at the tr file, it appears that there was already a directory 
confdir3 
    when you ran the strace step, and this directory messed up the test. Please 
    remove that directory (or rename it) and then re-run the "strace -o tr 
./a.out". 
    As before, the strace should also hang so you may need to type control-C to 
exit 
    it after a while. Look at the resulting 'tr' file and compare it to the 
    compressed file tr.gz I sent you earlier.

    > [Kelly] The difference of tr output start at:
    > 
    > openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3  ==> output from yours
    > 
    > openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3  ==> my 
output

    That difference is unimportant. I'm concerned more about what happens after 
the 
    long string of mkdir/chdir calls, which should occur once you get confdir3 
out 
    of the way.

tr
Description: tr