Re: "tcsetattr: Interrupted system call" after rapid-fire ^C chars

Chet Ramey wrote: > Joe Peterson wrote: > >> Well, without a hacked kernel, you'll probably not hit >> *this* manifestation of the issue, but what I did was: >> >> - run a text processing program (like "cat" or "tr")

"tcsetattr: Interrupted system call" after rapid-fire ^C chars

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/local

Bash tty session leader (tcsetpgrp) race condition - help requested

Hi all, I posted a bug report to bug-bash on June 21 about this seemingly long-standing problem, and I followed up with more info pointing to the cause a few days ago. I have not gotten any responses yet, and I am anxious to continue helping to find a solution. I am sorry not to include a patch

Re: stty sometimes hangs (ERESTARTSYS error) when called from .bashrc (cause discovered)

I have done more investigation, and I now know the cause of the bash/stty problem. It appears to be a race condition in bash (well, between two different bash shells, actually). I saw a post from a while back about something similar by Ingo Molnar, so I have copied him here too. Here is the ps t

stty sometimes hangs (ERESTARTSYS error) when called from .bashrc

From: Joe Peterson <[EMAIL PROTECTED]> To: bug-bash@gnu.org Subject: stty sometimes hangs (ERESTARTSYS error) when called from .bashrc Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DP

Re: bash strangeness with utf-8

Benno Schulenberg wrote: > No idea, I use Konsole. Better read man xterm. The strangeness happens in Konsole too (as well as the virtual terminals), so I kind of doubt it's the term's issue... > Okay. So what says a typescript in a blank shell with only LANG > defined? Does the ^[[1034h still

Re: bash strangeness with utf-8

Benno Schulenberg wrote: > On what terminal are you doing this? To what encoding is the > terminal set? Mainly xterm (version 225, at least in one case). And I have the utf8 option on. Does this set the encoding to the proper value, or do I need more? But also, I have tried this in the simple

bash strangeness with utf-8

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: freebsd6.2 Compiler: i686-gentoo-freebsd6.2-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='free bsd6.2' -DCONF_MACHTYPE='i686-gentoo-freebsd6.2' -DCONF_VENDOR='gentoo' -DLOCALE DIR