On 09/02/2010 08:25 AM, Eric Blake wrote:
Next, your trace showed the cause of the first message:
+mktempd_:51> template_length_=+mktempd_:1> wc -c
+mktempd_:51> template_length_=' 16'
+mktempd_:52> nx_=+mktempd_:1> echo gt-init.sh.
+mktempd_:52> nx_=+mktempd_:1> wc -c
+mktempd_:52> nx_=' 12'
+m
On Thu, Sep 02, 2010 at 08:25:51AM -0600, Eric Blake wrote:
> On 09/02/2010 08:02 AM, Tom G. Christensen wrote:
>
> >echo $BASH_VERSION
> >+ echo '3.1.16(1)-release'
> >3.1.16(1)-release
> >test $(echo y) = y || exit 1
> >cho y
> >++ cho y
> >bash: line 2: cho: command not found
> >+ test = y
> >b
On 09/02/2010 08:02 AM, Tom G. Christensen wrote:
> > zsh -vx ./test-vc-list-files-cvs.sh
> >
Sure, output here:
http://jupiterrise.com/tmp/zsh_vx_test-vc-list-files-cvs.out
Thanks. I definitely see a couple of problems.
First, there's no 'emulate sh' command anywhere in the trace, and zsh
On Wed, Sep 01, 2010 at 08:04:50PM -0600, Eric Blake wrote:
> On 09/01/2010 12:48 PM, Tom G. Christensen wrote:
> >+ exec zsh ./test-vc-list-files-cvs.sh --no-reexec
>
> Tom, since the reexec lost all tracing, what about:
>
> zsh -vx ./test-vc-list-files-cvs.sh
>
Sure, output here:
http://jupite
Eric Blake wrote:
...
> Tom, since the reexec lost all tracing, what about:
>
> zsh -vx ./test-vc-list-files-cvs.sh
>
> Jim, I'm wondering if init.sh should propagate v and/or x as part of
> the re-exec (certainly it would make it easier to get a full trace):
>
> opts=
> case $- in
> *v*) opts=v
