Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Deadlock when receiving kill-signal from child process
- X-seq: zsh-workers 35977
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Deadlock when receiving kill-signal from child process
- Date: Mon, 3 Aug 2015 13:58:18 -0700
- In-reply-to: <CA+=GgY5iZfgUag_V1jqmCv4=PUGBmaV2cNWTDjSO4DAZ+zm-iQ@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CA+=GgY7mHkyK4NJQ6m7y-HpVPKOuKx3-bkJqRHriKzZ662_iwA@mail.gmail.com> <150803085228.ZM24837@torch.brasslantern.com> <CA+=GgY5iZfgUag_V1jqmCv4=PUGBmaV2cNWTDjSO4DAZ+zm-iQ@mail.gmail.com>
On Aug 3, 11:36pm, Mathias Fredriksson wrote:
}
} I just tried applying this patch to 5.0.8 and I am still able to
} reproduce, occasionally zsh even exits with the following (maybe
} related):
}
} zsh: illegal hardware instruction ./zsh_deadlock.zsh
If you can get a stack trace from the deadlocked zsh, that would be
helpful.
A stack trace from the SIGILL's zsh might also be helpful, but that is
less likely.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author