From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
Date: Mon, 8 Oct 2018 17:43:55 +0100 [thread overview]
Message-ID: <20181008164357eucas1p28f2fd7942bffedcc4e769b2ad5d35c51~br9daEJcB1834618346eucas1p2w@eucas1p2.samsung.com> (raw)
In-Reply-To: <20181008154932.dvc5q46ylb66j2mm@tarpaulin.shahaf.local2>
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.
pws
next prev parent reply other threads:[~2018-10-08 16:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 21:05 [PATCH] typeset -p doesn't report -U (unique) attribute Stephane Chazelas
2018-09-25 16:41 ` Daniel Shahaf
2018-10-07 13:35 ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Stephane Chazelas
2018-10-08 9:05 ` Peter Stephenson
[not found] ` <CACeGjnUhNqca7jLAR0KKSxobzDd+xXdAe4BeUeRpxu2CTp_zkA@mail.gmail.com>
2018-10-08 14:10 ` Peter Stephenson
2018-10-08 14:28 ` Daniel Shahaf
2018-10-08 15:24 ` Peter Stephenson
2018-10-08 15:49 ` Daniel Shahaf
2018-10-08 15:57 ` Bart Schaefer
2018-10-08 16:06 ` Daniel Shahaf
2018-10-08 16:52 ` Bart Schaefer
2018-10-08 16:58 ` Peter Stephenson
2018-10-08 16:02 ` Daniel Shahaf
2018-10-08 16:19 ` Peter Stephenson
2018-10-08 16:43 ` Peter Stephenson [this message]
2018-10-08 16:58 ` Daniel Shahaf
2018-10-08 17:14 ` Bart Schaefer
2018-10-08 19:39 ` Stephane Chazelas
2018-10-09 9:02 ` Peter Stephenson
[not found] ` <1539075745.1499.2.camel@samsung.com>
2018-10-09 9:44 ` Peter Stephenson
2018-10-09 16:52 ` Bart Schaefer
2018-10-09 23:40 ` Vin Shelton
2018-10-08 15:54 ` Bart Schaefer
2018-10-08 16:40 ` Bart Schaefer
2018-10-09 10:59 ` local read-only variables (Was:[PATCH] [long] typeset doesn't report tied parameters (and related issues)) Stephane Chazelas
2018-10-11 9:45 ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Oliver Kiddle
2018-10-11 12:46 ` Peter Stephenson
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='20181008164357eucas1p28f2fd7942bffedcc4e769b2ad5d35c51~br9daEJcB1834618346eucas1p2w@eucas1p2.samsung.com' \
--to=p.stephenson@samsung.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).