From: Paul Eggert <eggert@cs.ucla.edu>
To: "Kelly Wang (kellythw)" <kellythw@cisco.com>,
Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>,
"Srini Garlapalli \(sgarlapa\)" <sgarlapa@cisco.com>,
"bug-rcs@gnu.org" <bug-rcs@gnu.org>,
"Yi Yan \(yyan\)" <yyan@cisco.com>
Subject: Re: rcs configure hang
Date: Mon, 26 Oct 2020 15:55:52 -0700 [thread overview]
Message-ID: <3a7010ae-04aa-6a65-83f4-aed2d77afc95@cs.ucla.edu> (raw)
In-Reply-To: <792D8329-891D-4191-B47F-0F14972E3D15@cisco.com>
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.
next prev parent reply other threads:[~2020-10-26 22:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B072F48-AF8B-47E0-AC5D-C9AB5E0DC4AD@cisco.com>
[not found] ` <873627odbp.fsf@gnuvola.org>
2020-10-22 22:02 ` rcs configure hang Paul Eggert
2020-10-26 16:13 ` Kelly Wang (kellythw)
2020-10-26 22:55 ` Paul Eggert [this message]
2020-10-27 15:36 ` Kelly Wang (kellythw)
2020-11-05 16:11 ` Kelly Wang (kellythw)
2020-11-05 17:57 ` Paul Eggert
2020-11-05 21:18 ` Kelly Wang (kellythw)
2020-11-05 21:36 ` Paul Eggert
2020-11-05 22:28 ` Kelly Wang (kellythw)
2020-11-05 22:52 ` Paul Eggert
2020-11-06 16:20 ` Kelly Wang (kellythw)
2020-11-06 17:40 ` Paul Eggert
2020-11-06 22:15 ` Kelly Wang (kellythw)
2020-11-09 9:14 ` Florian Weimer
2020-11-10 17:37 ` Kelly Wang (kellythw)
2021-01-11 16:19 ` Florian Weimer
2021-01-10 22:04 ` Thien-Thi Nguyen
2021-01-11 16:06 ` Kelly Wang (kellythw) via Gnulib discussion list
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a7010ae-04aa-6a65-83f4-aed2d77afc95@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=bug-rcs@gnu.org \
--cc=kellythw@cisco.com \
--cc=sgarlapa@cisco.com \
--cc=ttn@gnuvola.org \
--cc=yyan@cisco.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).