Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)

[Peter Stephenson <p.stephenson@xxxxxxxxxxx>]

On Mon, 2018-10-08 at 14:28 +0000, Daniel Shahaf wrote:
> Peter Stephenson wrote on Mon, 08 Oct 2018 15:10 +0100:
> I see a failure in a clean build on Debian stretch
> 
> [[[
> Test /home/daniel/src/zsh/./Test/V10private.ztst failed: bad status 139,
> expected 0 from:
>  if (( UID )); then
>    ZTST_verbose=0 $ZTST_exe +Z -f $ZTST_srcdir/ztst.zsh private.TMP/B02
>  else
>    ZTST_skip="cannot re-run typeset tests when tests run as superuser"
>  fi
> Was testing: typeset still works with zsh/param/private module loaded
> ]]]
> 
> It then says "2 failures, 2 skipped" even though no other failures are
> listed in the output.

Hmm, I'm guessing all the B02 failures are all down to being re-run from
V10?  That should be obvious from the output --- the first run of B02 is
much earlier.  Is that failing for anyone?  (This needs confirming.)

> This is with --enable-zsh-debug and modules compiled statically, if that
> matters.

Then there's even more you're not telling me --- V10 doesn't get
compiled in and would be skipped by default in this case.  However, I
updated the configuration and I'm still not seeing any problems myself.

As I'm not seeing problems, it's over to others --- include very much
fuller information if you want my help.  You'll need to narrow down
which tests are failing.  I suggest then running the code by hand ---
it's not clear from the above few lines what's failing there, so the key
may lie in private.TMP/B02.

There's a reasonable chance valgrind may help with the 139 status.  I
didn't get any hints from adding it to the combined V10 / B02 test,
however.

pws