Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/home/geoff/i686/share/locale' -DPACKAGE='bash' 
-DSHELL -DHAVE_CONFIG_H  -I.  -I.. -I../include -I../lib   -g -O2
uname output: Linux mica 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686 
i686 i386 GNU/Linux
Machine Type: i686-pc-linux-gnu

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
        When I run a pipeline such as "set | grep BASH", bash will hang.
        I did not have this problem at patch level 3.0.1.  (Is this a 
        side effect of the fix in patch bash30-012?)

        In gdb I see that control is looping from line 1869 through line
        1935 in wait_for() in jobs.c.  Both the "set" process and the "grep"
        process are defunct:

        geoff    22692  0.0  0.0     0    0 pts/2    Z+   17:22   0:00 [bash] 
<defunct>
        geoff    22693  0.0  0.0     0    0 pts/2    Z+   17:22   0:00 [grep] 
<defunct>

        Unfortunately I do not have the time to learn study the system
        long enough to understand why bash did not mark the processes as
        dead.

Repeat-By:
        %  set | grep BASH

-- 
Geoff Odhner <[EMAIL PROTECTED]>
Franklin Electronic Publishers


_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

Reply via email to