From: Andrew Owen <andrew.owen@principlestudios.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Strange terminal resizing behavior on macOS 11.6 and calling pwsh under zsh
Date: Wed, 6 Oct 2021 19:44:46 -0600 [thread overview]
Message-ID: <45857E5C-99C5-4834-ACCB-30570A2B910D@principlestudios.com> (raw)
In-Reply-To: <CAH+w=7bpeneYSNyETL3kwZhMHxkxUnaYSSSDPDkNAjYCBxAU2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
> On Oct 6, 2021, at 7:03 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Wed, Oct 6, 2021 at 4:06 PM Andrew Owen
> <andrew.owen@principlestudios.com> wrote:
>>
>> I seem to have found a curious bug in how zsh interacts with pwsh on macOS 11.6. I first reported it to the pwsh team, here: https://github.com/PowerShell/PowerShell/issues/16174
>
> I presume we can ignore the typo in
> https://github.com/PowerShell/PowerShell/issues/16174#issuecomment-934715868
> ("/usr/local/bin pwsh ...”).
Yes, that typo doesn’t exist in the actual script, Safari has some spell-correcting in place that misfires on occasion.
> I would suggest two things:
> 1) Examine the pwsh process with dtruss while attempting to reproduce
> the issue, to give some hint of whether QUIT is actually being
> received. Maybe you can figure out from where.
This is what I see when I target the zsh parent process (I got sidetracked with the pwsh process, which seems rather noisy from a syscall standpoint)
SYSCALL(args) = return
dtrace: error on enabled probe ID 1657 (ID 258: syscall::sigprocmask:return): invalid user access in action #5 at DIF offset 0
dtrace: error on enabled probe ID 1657 (ID 258: syscall::sigprocmask:return): invalid user access in action #5 at DIF offset 0
dtrace: error on enabled probe ID 2212 (ID 270: syscall::ioctl:return): invalid user access in action #5 at DIF offset 0
dtrace: error on enabled probe ID 2082 (ID 530: syscall::sigreturn:return): invalid user access in action #5 at DIF offset 0
> 2) Try using "exec /usr/local/bin/pwsh ..." in the script so the zsh
> parent is removed from the process tree, and then try to reproduce the
> issue.
This makes it so that the reproduction steps I listed before no longer lead to the crash.
[-- Attachment #2: Type: text/html, Size: 4238 bytes --]
next prev parent reply other threads:[~2021-10-07 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 23:05 Andrew Owen
2021-10-07 1:03 ` Bart Schaefer
2021-10-07 1:44 ` Andrew Owen [this message]
2021-10-07 2:51 ` Bart Schaefer
2021-10-07 2:58 ` Andrew Owen
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=45857E5C-99C5-4834-ACCB-30570A2B910D@principlestudios.com \
--to=andrew.owen@principlestudios.com \
--cc=schaefer@brasslantern.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).