[Bug 892317] [NEW] set -e reverses order of signal handlers

[solidsnack]

Public bug reported:

When `-e` is not specified, an INT signal handler runs before an EXIT
signal handler; when -e is specified, the EXIT signal handler is run
(but only one of its statements) and then the INT signal handler is run.

:;  /bin/dash < ./trap.sh 
^Ctrapped: SIG_
trapped: EXIT 2
next part
:;  /bin/dash -e < ./trap.sh 
^Ctrapped: EXIT 130
trapped: SIG_

With `bash --posix` or `busybox sh`, the order of signal handlers is the
same no matter whether `-e` is specified or no. Please see the attached
script, `trap.sh`.

** Affects: dash
     Importance: Undecided
         Status: New

** Affects: dash (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/892317

Title:
  set -e reverses order of signal handlers

Status in dash - The Debian Almquist Shell:
  New
Status in “dash” package in Ubuntu:
  New

Bug description:
  When `-e` is not specified, an INT signal handler runs before an EXIT
  signal handler; when -e is specified, the EXIT signal handler is run
  (but only one of its statements) and then the INT signal handler is
  run.

  :;  /bin/dash < ./trap.sh 
  ^Ctrapped: SIG_
  trapped: EXIT 2
  next part
  :;  /bin/dash -e < ./trap.sh 
  ^Ctrapped: EXIT 130
  trapped: SIG_

  With `bash --posix` or `busybox sh`, the order of signal handlers is
  the same no matter whether `-e` is specified or no. Please see the
  attached script, `trap.sh`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash/+bug/892317/+subscriptions