From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: zsh-workers-return-43477-ml=inbox.vuxu.org@zsh.org
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE
	autolearn=ham autolearn_force=no version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id 49d1fe28
	for <ml@inbox.vuxu.org>;
	Mon, 17 Sep 2018 14:02:10 +0000 (UTC)
Received: (qmail 16845 invoked by alias); 17 Sep 2018 14:01:57 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 43477
Received: (qmail 28198 invoked by uid 1010); 17 Sep 2018 14:01:57 -0000
X-Qmail-Scanner-Diagnostics: from mail-oi0-f68.google.com by f.primenet.com.au (envelope-from <sgniazdowski@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.218.68):SA:0(-1.9/5.0):. 
 Processed in 4.564655 secs); 17 Sep 2018 14:01:57 -0000
X-Envelope-From: sgniazdowski@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=WiO4IKf5Z6bn79WSgivsUuhJgvfvB8jsXHWQlGHnpg8=;
        b=cvTOfed1prwnSDtLilfZzlG2QHHmB4YBAHAOqvtHdkY74jhTa8h3r5s+X6blyQkhKU
         KLTSTDR0SukEvgOhTWSgjXcQPaFOvjozctw+pQqnHFjGhE4r4CquFCaR2k9u6VX1LnDU
         t5K5YUsJw51qli/yB+wXLhkY9aPV6V9Vz+2O+ce+NPlkHi72WEBYA9OzNrsALKcGSixO
         Z6QdfR1SiKMu/QX4+LX9x6UH4bHLXbyLAlBhfXDiPal4JdyiRz0mWjgr/8CQAuk8kRlG
         HesCEtPjTCV35V2MwNklqowYebGqzCs5G+4sO9pAsuWl5EU52Yc7KdKYOtuOE/DkGmqy
         +mVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=WiO4IKf5Z6bn79WSgivsUuhJgvfvB8jsXHWQlGHnpg8=;
        b=UEqUoM5dLPQtYugkYRNkN9DH5QFIbUkXWFCiddoN9xH4NKqZ8pDHqT41h9heko8mlM
         6jyN6EYek6URiNFNSAhy84J3SSfbiMjNN0XWMSaCbH/ccvU62mXqdeQA8ssepTUJ6rfc
         ax+14Tz+w5UGBS5p17uUHVIP2RNt9HVYD9Zs4wmxmfROfqhjOCh9BpNI8Ipz3u5kMujG
         BVm6hLiXFPeSordYZpJXz9Hq7JnZI1I7zVMRb5G/0NFFt9QWElG5eZSKS0u4WSk5Txdz
         UwS04/CUoqtVpc6kGSLbH4x+4e7VZVpUfa20jb+m0z3BNd+fMJZTCUMDyzDpItdiyPSS
         cYVA==
X-Gm-Message-State: APzg51CquLCBbO6SyZZN460E/FtNOHPofEeL+4BXGPO9fw/PU8aAKzo9
	zTPzImd1JIOr/qg3gkLxcVnlyMPuY4mfnoAa+b8Tqw==
X-Google-Smtp-Source: ANB0VdYw4KURRdhjbWsPgXqfYAUOUr9YtGvYA8UmPowJSNY986r3D6vgbLt6xPdsVDhEo4ntu0XnpySXgAi7QVsJDXA=
X-Received: by 2002:aca:f383:: with SMTP id r125-v6mr18453045oih.6.1537192909046;
 Mon, 17 Sep 2018 07:01:49 -0700 (PDT)
MIME-Version: 1.0
References: <ef42fe7f-4ecf-4dbc-cdb0-2d6e4cf27377@xk2c.de>
In-Reply-To: <ef42fe7f-4ecf-4dbc-cdb0-2d6e4cf27377@xk2c.de>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Mon, 17 Sep 2018 16:01:36 +0200
Message-ID: <CAKc7PVAsJXv=jxcbrENM4LtcBkz86mbVe3WgCYBs6cwdEO=9hQ@mail.gmail.com>
Subject: Re: Zsh: [7] + 23074 suspended (tty output)
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

Hello
Allow me to do this broken record writing, but wouldn't it be nice to
have Valgrind automatic tests prepared for a handy run while doing the
`suspended tty' investigation and patching? The VATS (Valgrind
Automatic Tests Suite) can be still added to upstream. It is just a
copy of Test directory, I know this doesn't sound nice, but also:
definition-files with non-harmful, already known Valgrind errors, and
a Zsh script that parses Valgrind output doing some hiding,
formatting, etc.
On Sat, 15 Sep 2018 at 19:42, TS <debts@xk2c.de> wrote:
>
> Hello,
>
> i am not subscribed, please cc me.
>
> in this bugreport
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908818
>
> i reported an issue with Zsh 5.6. Debian maintainers asked to report
> directly. So here it goes.
>
> The shortest test case i could come with is documented in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908818#66
>
> Basically its a setup for startup profiling which did work up to 5.5.1
> but since 5.6 instead of displaying profiling data zsh says:
>
> zsh: suspended (tty output)
>
> i then have to 'fg' first to see the actual profiling data.
>
>
>
>
> kind regards,
>
>      Thilo
>


-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org