sudo crashed with SIGSEGV in kill()

[Aram Paronikyan]

In contrast to the https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1618602 , this happened for 17.04 also

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: sudo 1.8.19p1-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Feb 28 17:53:02 2017
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2013-09-15 (1262 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: sudo gdebi-gtk
Signal: 11
SourcePackage: sudo
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 __libc_start_main (main=0x56386061da50, argc=2, argv=0x7ffee81c3e58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffee81c3e48) at ../csu/libc-start.c:291
 ?? ()
Title: sudo crashed with SIGSEGV in kill()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK
 /etc/sudoers.d/libertine-lxc-sudo: parsed OK
 /etc/sudoers.d/unity8-lxc: parsed OK

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1663453, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.