Confirmed, this is caused by the following change in behaviour:

When the command sudo is running dies due to a signal, sudo will now
send itself that same signal with the default signal handler installed
instead of exiting. The bash shell appears to ignore some signals, e.g.
SIGINT, unless the command being run is killed by that signal. This
makes the behavior of commands run under sudo the same as without sudo
when bash is the shell. Bug #722.

This makes a process receiving a SIGABRT cause sudo to exit with the
same failure.

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

Title:
  sudo crashed with SIGABRT in kill()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to