Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc -I/usr/src/packages/BUILD/bash-4.1
-L/usr/src/packages/BUILD/bash-4.1/../readline-6.1
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-suse-linux-gnu'
-DCONF_VENDOR='suse' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CONFIG_H -I. -I. -I./include -I./lib -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g -dH -D_GNU_SOURCE -DRECYCLES_PIDS -Wall -g
-std=gnu89 -Wuninitialized -Wextra -Wno-unprototyped-calls -Wno-switch-enum
-Wno-unused-variable -Wno-unused-parameter -ftree-loop-linear -pipe
-fprofile-use
uname output: Linux oct 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10
+0100 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-suse-linux-gnu
Bash Version: 4.1
Patch Level: 10
Release Status: release
Description:
Warning "execute_coproc: coproc [$PID:.*] still exists" as it is
implemented makes no sense. It appears in many situations where
it is done intentionally and it is not easy to silence it.
If writing values of PID and I/O channels does not overwrite old
values, I see no reason to issue this warning.
Repeat-By:
coproc a ( cat )
coproc b ( cat )
bash: warning: execute_coproc: coproc [13690:b] still exists
Fix:
The warning should be issued only if the old process still
exists AND array which should store the coproc data is not
empty (or only if the array is not empty).
