sudo crashed with SIGSEGV in kill()

[Thomas A. F. Thorne]

Logged into a machine and I was informed of an error. There is not much way for me to say what triggered it until the diags are presented. If the suggested bugs of #1565332, #1618602, #312835 and #1659846 are anything to go by the diagnostics are not going to reveal anything either.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.3
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 27 12:19:57 2017
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2015-03-12 (752 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: sudo ./test -t Timer
Signal: 11
SourcePackage: sudo
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 __libc_start_main (main=0x55e026690a20, argc=4, argv=0x7ffffecec8c8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffffecec8b8) 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
mtime.conffile..etc.sudoers: 2016-07-11T15:06:58.741085

[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.

[Thomas A. F. Thorne (tafthorne)]

Oh good. Another bug that has been marked as a duplicate of a private bug so I cannot tell if it should or should not be a duplicate of it.

This bug is not marked as private any more. Please can someone with access to #1663453 check if it should or should not be still marked as private.