Re: Help me track down a tough bug? (probably funcfiletrace, subshells and possibly I/O redirection)

[Peter Stephenson <pws@xxxxxxx>]

On Mon, 29 Sep 2008 20:18:52 -0400
"Rocky Bernstein" <rocky.bernstein@xxxxxxxxx> wrote:
> zshdb<3> p ${funcfiletrace[@]}
> 
> ./command/eval.sh:11 ./command/eval.sh:27 ./lib/processor.sh:96
> ./lib/processor.sh:44 ./zshdb2.sh:9 ./testing.sh:3 ./zshdb2.sh:34
> ./command/eval.sh:11 ./command/eval.sh:27 ./lib/processor.sh:96
> ./lib/processor.sh:44 ./zshdb2.sh:9 ./testing.sh:3 ./zshdb2.sh:34
> ./zshdb2.sh:9 ./testing.sh:3 ./zshdb2.sh:34
> # Were did that double set of lines come from?

Hmmm... I'm not convinced this has got anything directly to do with the
shell rather than the debugger.  Here's what I get when I simply ask for
the PID repeated times:

---------------
./zshdb2.sh:7 ./zshdb2.sh:34
===============
(./zshdb2.sh:34):
. ./testing.sh
./zshdb2.sh:9 ./zshdb2.sh:34
zshdb<1> p $$
711
./zshdb2.sh:9 ./zshdb2.sh:34
zshdb<2> p $$
711
711
./zshdb2.sh:9 ./zshdb2.sh:34
zshdb<3> p $$
711
711
711
./zshdb2.sh:9 ./zshdb2.sh:34
zshdb<4> 

It looks like something is odd with whatever is holding the command to be
executed.  You know better than me how that works.

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070