All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jeff King <peff@peff.net>, Git List <git@vger.kernel.org>
Subject: Re: How do I run tests under Valgrind?
Date: Fri, 21 Sep 2012 22:13:09 +0200	[thread overview]
Message-ID: <505CCA55.6030609@gmail.com> (raw)
In-Reply-To: <CALkWK0kWvrirPjXXzBBBQxKDcwpd_+nQ2eeT6SE8gDFW5T7WFQ@mail.gmail.com>

On 09/21/2012 09:58 PM, Ramkumar Ramachandra wrote:
> Hi again,
> 
> Ramkumar Ramachandra wrote:
>> I was able to reproduce the problem on all my machines, and I consider
>> this very disturbing.  However, I was successfully able to corner the
>> issue. I have an overtly long $PATH that's not getting split properly
>> by `IFS=:` in one corner case -- in other words, this shell script
>> fails to execute properly when called with `--tee` (just set a really
>> long $PATH and try):
> 
> Oops.  Looks like it has nothing to do with an overtly long $PATH.  It
> has something to do with $SHELL being zsh though, because other shells
> work.  Looking deeper into this.
> 
Zsh doesn't do word-splitting by default on variable expansions:

    $ zsh -c 'v="1 2 3"; for x in $v; do echo "$x"; done'
    1 2 3

unless you set the SH_WORD_SPLIT option, or put Zsh in Bourne-compatibility
mode somehow:

    $ zsh -o SH_WORD_SPLIT -c 'v="1 2 3"; for x in $v; do echo "$x"; done'
    1
    2
    3

    $ zsh -c 'emulate sh; v="1 2 3"; for x in $v; do echo "$x"; done'
    1
    2
    3

More info at: <http://zsh.sourceforge.net/FAQ/zshfaq02.html>

HTH,
  Stefano

  reply	other threads:[~2012-09-21 20:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 17:01 How do I run tests under Valgrind? Ramkumar Ramachandra
2012-09-17 17:20 ` Jeff King
2012-09-17 17:23   ` Ramkumar Ramachandra
2012-09-17 17:35     ` Jeff King
2012-09-17 17:39       ` Ramkumar Ramachandra
2012-09-17 17:44         ` Jeff King
2012-09-17 17:55           ` Johannes Sixt
2012-09-17 17:57             ` Jeff King
2012-09-17 18:28           ` Ramkumar Ramachandra
     [not found]           ` <CALkWK0mkBbY7dUyaZAqqKE3ZMfE_xU6em_KCOKM9nsTjUP-9pA@mail.gmail.com>
2012-09-17 18:29             ` Jeff King
2012-09-21 19:31               ` Ramkumar Ramachandra
2012-09-21 19:58                 ` Ramkumar Ramachandra
2012-09-21 20:13                   ` Stefano Lattarini [this message]
2012-09-21 20:17                     ` Ramkumar Ramachandra
2012-09-21 20:46                       ` Ramkumar Ramachandra
2012-09-21 20:49                     ` Jeff King
2012-09-22 13:03                       ` Stefano Lattarini
2012-09-22 17:47                         ` Jeff King
2012-09-22 18:20                           ` Stefano Lattarini
2012-09-22 20:24                           ` Junio C Hamano
2012-09-21 20:52                     ` [PATCH] t/test-lib.sh: do not trust $SHELL Ramkumar Ramachandra
2012-09-21 20:58                       ` Jeff King
2012-09-21 21:07                         ` Ramkumar Ramachandra
2012-09-21 21:12                           ` Jeff King
2012-09-21 21:34                             ` Ramkumar Ramachandra
2012-09-21 21:57                               ` Andreas Schwab
2012-09-21 22:30                                 ` Junio C Hamano
2012-09-22  4:26                                   ` Ramkumar Ramachandra
2012-09-22  4:52                                     ` Junio C Hamano
2012-09-22  4:54                                       ` Ramkumar Ramachandra
2012-09-22  4:57                                         ` Ramkumar Ramachandra
2012-09-22 20:16                                           ` Junio C Hamano
2012-09-26  3:49                                             ` Ramkumar Ramachandra
2012-09-21 21:59                               ` Junio C Hamano
2012-09-21 22:15                               ` Jeff King
2012-09-21 21:08                         ` Andreas Schwab
2012-09-21 21:13                           ` Jeff King

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=505CCA55.6030609@gmail.com \
    --to=stefano.lattarini@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.