From: Anand N <anand.mail@gmail.com>
To: zsh-workers@zsh.org
Subject: Fwd: Issue with echo & source to /dev/stdin
Date: Wed, 6 Jan 2021 22:40:16 +0530 [thread overview]
Message-ID: <CAH=D2eO30vMaxHJNi4eMeOGG2bCHcjKeDjpv+thwig=fxBQVqg@mail.gmail.com> (raw)
In-Reply-To: <CAH=D2ePreSUi9VSDqZsXVjAJZbte5ui5c60BMvERRK4gCiZnbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
+zsh-workers@zsh.org <zsh-workers@zsh.org>
---------- Forwarded message ---------
From: Anand N <anand.mail@gmail.com>
Date: Wed, Jan 6, 2021 at 10:39 PM
Subject: Re: Issue with echo & source to /dev/stdin
To: Bart Schaefer <schaefer@brasslantern.com>
Hi Bart,
I tried with dtruss; but it was giving error for built-ins
dtrace: failed to execute echo: (os/kern) failure
There might be other ways, but I am no expert in shell and dtruss.
Please let me know if I can do anything else.
Regarding the discussion in nvm github, can you please post your query over
there?
Like I mentioned above, I am no expert and your inputs there will help the
others in the discussion as well
Thanks,
Anand
On Wed, Jan 6, 2021 at 10:10 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Tue, Jan 5, 2021 at 10:27 PM Anand N <anand.mail@gmail.com> wrote:
> >
> > We noticed that even a very basic echo to /dev/stdin is taking more than
> 5 seconds.
>
> Has anyone tried using "dtruss" on the process to see which system
> calls may be blocking?
>
[-- Attachment #2: Type: text/html, Size: 3752 bytes --]
next prev parent reply other threads:[~2021-01-06 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 6:27 Anand N
2021-01-06 16:40 ` Bart Schaefer
[not found] ` <CAH=D2ePreSUi9VSDqZsXVjAJZbte5ui5c60BMvERRK4gCiZnbA@mail.gmail.com>
2021-01-06 17:10 ` Anand N [this message]
2021-01-06 20:41 ` Bart Schaefer
2021-01-06 16:48 ` Bart Schaefer
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='CAH=D2eO30vMaxHJNi4eMeOGG2bCHcjKeDjpv+thwig=fxBQVqg@mail.gmail.com' \
--to=anand.mail@gmail.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).