Package: mksh
Version: 46-1
Severity: normal
When running a command that traps SIGINT, mksh doesn't ignore SIGINT.
It should implement WCE (like bash and ksh93), as described on:
http://www.cons.org/cracauer/sigint.html
To reproduce the bug:
mksh -c gdb; echo OK
and type Ctrl-C (trapped by gdb), then Ctrl-D to quit gdb. OK is not
output and echo $? outputs 130 instead of 0.
With this bug, mksh shouldn't be a /bin/sh candidate, as this bug can
yield spurious command failure when executed with system().
Note that due to a mksh optimization, the bug does not appear when
there is a single command: in such a case, the shell does not fork,
but executes the command, replacing it, so that the shell is no longer
involved.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mksh depends on:
ii libc62.17-3
ii libgcc1 1:4.8.0-7
mksh recommends no packages.
Versions of packages mksh suggests:
ii ed 1.8-1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
