From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8369 invoked by alias); 11 Dec 2011 14:38:28 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 29997 Received: (qmail 29699 invoked from network); 11 Dec 2011 14:38:25 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at bewatermyfriend.org does not designate permitted sender hosts) From: Frank Terbeck To: zsh-workers@zsh.org Subject: Re: $pipestatus broken? In-Reply-To: <111210065833.ZM6198@torch.brasslantern.com> (Bart Schaefer's message of "Sat, 10 Dec 2011 06:58:33 -0800") References: <87borgzkap.fsf@ft.bewatermyfriend.org> <877h24zj69.fsf@ft.bewatermyfriend.org> <111210065833.ZM6198@torch.brasslantern.com> User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.91 (gnu/linux) Date: Sun, 11 Dec 2011 15:37:10 +0100 Message-ID: <87vcpnw4x5.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: NDMwNDQ0 Bart Schaefer wrote: [...] > With that loop, I get a single "1" 100% of the time unless I attach to > the process with GDB, in which case it becomes random. I know I won't be much help in solving this, because I don't know how any of the job handling code works or even what needs to be done for any sort of sane job handling in the first place... But I tried to see if I could pinpoint the revision, that introduced the breakage. And it appears, that the first release that featured `$pipestatus' was 3.1.7. And it's broken in that release already. The first tag that includes the feature is `zsh-3.1.6-dev-21'. I tried to build it, but I can't get the autotools (I tried various versions) to produce a valid `configure' script. :-/ `$pipestatus' was introduced in workers-10358: Regards, Frank