[bash 2.05b] Readline F1..F4 in xterm

[Ingo van Lil]

Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib  -g -O2
uname output: Linux marvin 2.4.21 #7 Sun Aug 10 13:39:23 CEST 2003 i586 unknown
Machine Type: i586-pc-linux-gnu

Bash Version: 2.05b
Patch Level: 0
Release Status: release

Description:
        A few days ago I upgraded my bash 2.03 to 2.05b, mainly to
        benefit of the new programmable completion features. Anyway, I
        noticed a bug that seems to be quite critical: Whenever I enter
        a sequence that begins with <esc>O and that is not mapped to any
        function bash runs berserk and eats up all CPU cycles and
        memory, until I stop it by hitting <ctrl-c> or the kernel
        finally kills the process. I noticed that because my xterm maps
        F1 .. F4 to "\eOP" .. "\eOS".
        According to a backtrace I made bash gets caught in endless
        recursion between

        _rl_dispatch (key=256, map=0x811f008) at readline.c:529

        and

        _rl_dispatch_subseq (key=256, map=0x811f008, got_subseq=0) at
                readline.c:570

Repeat-By:
        Simple: Run bash without any inputrc file and enter <Esc>OP.

        HTH,
          Ingo