bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bash 3.0 ignores intr character


From: Tim Mooney
Subject: Re: bash 3.0 ignores intr character
Date: Wed, 11 Aug 2004 16:38:03 -0500 (CDT)

In regard to: Re: bash 3.0 ignores intr character, Chet Ramey said (at...:

Tim Mooney wrote:

Configuration Information [Automatically generated, do not change]:
Machine: alphaev56
OS: osf5.1
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='alphaev56' -DCONF_OSTYPE='osf5.1' -DCONF_MACHTYPE='alphaev56-dec-osf5.1' -DCONF_VENDOR='dec' -DLOCALEDIR='/local/gnu/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -I/local/gnu/include -std -O3 -g3 -tune host -arch host -Olimit 3000 -portable -readonly_strings -msg_disable inlinestoclsmod,valuepres,longlongtype
uname output: OSF1 dogbert V5.1 2650 alpha
Machine Type: alphaev56-dec-osf5.1

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

Description:

        but it seems to have completely broken intr-handling in bash 3.0.

No.  Something else is at fault.  I'm traveling and don't have access to
Solaris 2.8, but can't reproduce it right now on the systems to which I
do have access.

Does ^C work to interrupt a normal process?  For example, can you
interrupt a `sleep' job with ^C?

No.  On Tru64 when I try

        echo $$; sleep 99

in a bash 3.0 window, pressing ^C does nothing.  It also doesn't show up
in truss, so it's never getting to bash.  Pressing e.g. ^Z does.

On Solaris, the only difference is that at least ^C is echoed to my
screen, though it doesn't interrupt the sleep *and* it doesn't show up in
a truss of bash.

When running a system call tracer like `truss', does pressing ^C while
readline is active even generate a SIGINT?

No.

Tim
--
Tim Mooney                              address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164




reply via email to

[Prev in Thread] Current Thread [Next in Thread]