From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug in ZSH 5.0.0 - Segmentation fault after sending process to background
Date: Thu, 11 Oct 2012 08:52:44 -0700 [thread overview]
Message-ID: <121011085244.ZM31700@torch.brasslantern.com> (raw)
In-Reply-To: <CAECNH1TC6yo8L_WAwTU2KHLDPYuiyEh_=RG6s_YKaKKj+7sObQ@mail.gmail.com>
On Oct 11, 3:35pm, Peter Stephenson wrote:
}
} I've added some tests to ensure thisjob is valid where necessary, and
} also ensured that it's not valid for code called from execsimple(),
} since it's never been set up --- or if it has we have no reason to
} suppose it's a job we're interested in.
Well, drat. I was hoping this had some bearing on the pipestatus bug
(workers/29973) but it appears not.
prev parent reply other threads:[~2012-10-11 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:46 BlueC0re
2012-10-11 14:35 ` Peter Stephenson
2012-10-11 15:52 ` Bart Schaefer [this message]
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=121011085244.ZM31700@torch.brasslantern.com \
--to=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).