continued job is treated as stopped job

[Christian von Ferber]

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: Linux
Compiler: gcc
Compilation CFLAGS:   -DHAVE_VFPRINTF -DHAVE_UNISTD_H -DHAVE_STDLIB_H
-DHAVE_LIMITS_H        -DHAVE_GETGROUPS -DHAVE_RESOURCE -DHAVE_SYS_PARAM
-DVOID_SIGHANDLER -DHAVE_GETDTABLESIZE -DHAVE_BCOPY -DHAVE_GETPW_DECLS
-DHAVE_GETHOSTNAME -DHAVE_WAIT_H         -DHAVE_DUP2 -DHAVE_STRERROR
-DHAVE_DIRENT_H -DHAVE_STRING_H        -DHAVE_VARARGS_H -DHAVE_STRCHR
-DHAVE_DEV_FD        -Di386 -DLinux -DSHELL -DHAVE_ALLOCA -DHAVE_ALLOCA_H
-O2 -march=i386 -mcpu=i686
uname output: Linux cerbo 2.2.16-3smp #1 SMP Mon Jun 19 19:00:35 EDT 2000
i686 unknown

Bash Version: 1.14
Patch Level: 7

Description:

        A stopped job that is continued by the CONT signal "kill -CONT %1"
        is treated by bash as still being stopped even though it is
        running. Only "bg %1" will update the jobs list correctly.

        In particular when exiting the shell the running job will be
        killed.

Repeat-By:

        $ ./myjob &
        [1] 26911
        $ kill -STOP myjob

        [1]+  Stopped (signal)        ./myjob
        $ kill -CONT myjob

        [1]+  Stopped (signal)        ./myjob
        $ jobs
        [1]+  Stopped (signal)        ./myjob

        $ ps o stat,cmd              # note that myjob is actually running
        STAT CMD
        R    ./myjob

        $ exit
        exit
        There are stopped jobs.