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

[Daniel Shahaf <d.s@daniel.shahaf.name>]

Peter Stephenson wrote on Mon, 08 Oct 2018 17:43 +0100:
> On Mon, 2018-10-08 at 15:49 +0000, Daniel Shahaf wrote:
> > Peter Stephenson wrote on Mon, Oct 08, 2018 at 16:24:04 +0100:
> > > 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.
> > I did.  If someone wants to look into it (not necessarly Peter), be my
> > guest.
> > 
> > ==25895== Invalid read of size 8
> > ==25895==    at 0x4823AE: zshlex (lex.c:280)
> > ==25895==    by 0x4ACBC0: parse_event (parse.c:581)
> > ==25895==    by 0x47109D: loop (init.c:146)
> > ==25895==    by 0x47659B: zsh_main (init.c:1757)
> > ==25895==    by 0x420201: main (main.c:93)
> > ==25895==  Address 0x3a is not stack'd, malloc'd or (recently) free'd
> 
> If your lex.c is like mine, I don't think this is telling us anything
> directly relevant --- presumably the damage has been done.  That's
> dereferencing the list of here documents previously built up, which is
> nothing to do with the change.

So the lex.c error may be an independent issue.  The link to the typeset
change is probably the failure address, 0x3A, which is the hex value of
the ASCII colon character, which is the joinchar of $MANPATH.