GW$BA0$KAj
$B%\%?%s$R$H$D$GL5NA$G(B1$B1_J,$bM7$Y$^$9!#(B 1$B1_J,$"$l$PNA6b$,[EMAIL PROTECTED]($^$9!#(B $B:#$9$0$K$G$b;n$7$F$_$F2<$5$$!#(B http://awg.webchu.com/?springh ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Use of arrows to scroll history list not same.
pete Spam-Avoider wrote: > > Configuration Information [Automatically generated, do not change]: > Machine: i686 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='linu > x-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' > -DLOCALEDIR='/usr/ > share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include > -I. > /lib -g -O2 > uname output: Linux parallax 2.6.11 #1 SMP Sat Apr 2 18:08:45 EST 2005 i686 > unkn > own unknown GNU/Linux > Machine Type: i686-pc-linux-gnu > > Bash Version: 3.0 > Patch Level: 0 > Release Status: release > > Description: > In upgrading from bash-2.04 to bash-3.0 i'm experiencing a > change in the behaviour of the up/down arrow keys to scroll > through the history list of an interactive shell. The > behaviour for bash-2.04 was that i could scroll up from and > then back down to a blank line. For bash-3.0 if i scroll up > only one line and back down i can return to a blank line, > however, if i scroll up more then one line then i can not > return to a blank line, instead some near random line of the > lines i had passed over remains at the prompt and not a blank > line. > > > Repeat-By: > Scroll up and down through the history list and see if > you can return down to a blank line. Apply the patches to bash-3.0. Patch 5 fixes this problem. ftp://ftp.cwru.edu/pub/bash/bash-3.0-patches/bash30-005 ftp://ftp.gnu.org/pub/gnu/bash/bash-3.0-patches/bash30-005 Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
processes hanging in STOPPED state
Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 uname output: Linux neurosis 2.6.11 #1 Fri Mar 4 13:53:50 EST 2005 i686 GNU/Linux Machine Type: i386-pc-linux-gnu Bash Version: 3.0 Patch Level: 16 Release Status: release Description: Bug at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224543 (reported back on 2.05) still exists on 3.0... re-reporting to bug-bash so hopefully it gets noticed. Bash is apparently improperly setting up process groups in a way that causes processes to become stuck in the STOPPED state. Repeat-By: env -i EDITOR=emacs TERM=linux SHELLOPTS=monitor bash --noprofile --norc -c "while true; do crontab -e ; done" Hit ^X ^C rapidly to keep exiting emacs. Soon, a copy hangs on startup, process in stopped state (T), cannot be restarted with SIGCONT, only killed with SIGKILL. Fix: http://groups-beta.google.com/group/linux.kernel/msg/757fd571c7cecc35 ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: processes hanging in STOPPED state
> Bash Version: 3.0 > Patch Level: 16 > Release Status: release > > Description: > Bug at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224543 > (reported back on 2.05) still exists on 3.0... re-reporting > to bug-bash so hopefully it gets noticed. > > Bash is apparently improperly setting up process groups in > a way that causes processes to become stuck in the STOPPED > state. And did changing the definition of PGRP_PIPE in config.h solve the problem? Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: processes hanging in STOPPED state
Chet Ramey wrote: > > Bash is apparently improperly setting up process groups in > > a way that causes processes to become stuck in the STOPPED > > state. > > And did changing the definition of PGRP_PIPE in config.h solve the problem? Yes, defining PGRP_PIPE does appear to make the problem go away. But the previously referenced post from Linus said that PGRP_PIPE may cause other problems, and that there exists a "proper fix" that you have not yet included in the bash sources? As before, I cannot find that patch, do you have it? -jim ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
