From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: zsh-workers@zsh.org
Subject: Re: Segfault in =( ) substitution
Date: Fri, 21 Dec 2012 17:51:01 +0800 [thread overview]
Message-ID: <20121221095101.GH2464@localhost.localdomain> (raw)
In-Reply-To: <20121221090126.GG2464@localhost.localdomain>
On Fri, Dec 21, 2012 at 05:01:26PM +0800, Han Pingtian wrote:
>
> commit ad92cb3203e5d95be91019633e8f1f5835b12794
> Author: Peter Stephenson <pws@users.sourceforge.net>
> Date: Thu Oct 11 16:36:14 2012 +0000
>
> 30724: shell code optimisd to use execsimple() doesn't have a valid
> thisjob
>
> diff --git a/ChangeLog b/ChangeLog
> index 9768aa8..5a69f01 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,8 @@
> +2012-10-11 Peter Stephenson <pws@csr.com>
> +
> + * 30724: Src/exec.c, Src/jobs.c: shell code optimised to use
> + execsimple() doesn't have a valid thisjob.
> +
> 2012-10-09 Peter Stephenson <pws@csr.com>
>
> ... ...
And it looks like I cannot reproduce the crash reported in 30723 with
the build without this commit at all. Maybe the problem of 30723 isn't
caused by reasons we trusted at that time?
I first checkout a 'detached HEAD' by 'git checkout 34ed3ea', where the
34ed3ea commit is just before ad92cb3 commit. And it looks the build
works just fine:
localhost% cat ./t.sh
precmd () {
{}
}
localhost% source t.sh
localhost% type -f precmd
precmd () {
{
}
}
localhost% sleep 50 &; sleep 30
[1] 10503
^Z
zsh: suspended sleep 30
localhost%
[1] - done sleep 50
localhost%
Please correct me if I'm missing something here. Thanks.
next prev parent reply other threads:[~2012-12-21 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 3:30 Vin Shelton
2012-10-15 9:07 ` Peter Stephenson
2012-10-17 19:20 ` Peter Stephenson
2012-10-17 20:16 ` Peter Stephenson
2012-10-18 15:07 ` Bart Schaefer
2012-10-18 15:27 ` Peter Stephenson
2012-12-21 7:57 ` Han Pingtian
2012-12-21 9:01 ` Han Pingtian
2012-12-21 9:51 ` Han Pingtian [this message]
2012-12-21 10:34 ` 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=20121221095101.GH2464@localhost.localdomain \
--to=hanpt@linux.vnet.ibm.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).