sudo crashed with SIGSEGV in kill()

Bug #1618602 reported by Cristian Aravena Romero
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crash.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: sudo 1.8.16-0ubuntu3
Uname: Linux 4.8.0-040800rc3-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug 30 16:28:52 2016
ExecutablePath: /usr/bin/sudo
InstallationDate: Installed on 2015-07-26 (401 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
ProcCmdline: sudo ./unetbootin-linux64-625.bin
Signal: 11
SourcePackage: sudo
StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 __libc_start_main (main=0x55f06eca89f0, argc=2, argv=0x7fffb1bcfdc8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb1bcfdb8) at ../csu/libc-start.c:291
 ?? ()
Title: sudo crashed with SIGSEGV in kill()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 kill () at ../sysdeps/unix/syscall-template.S:84
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /build/sudo-KZY_jC/sudo-1.8.16/src/sudo.c:330

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in sudo (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sudo (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

This seems more likely an issue with the unetbootin script. It'd be good to know what it was doing and then try and recreate the crash using sudo itself.

ProcCmdline: sudo ./unetbootin-linux64-625.bin

Changed in sudo (Ubuntu):
status: Confirmed → Incomplete
tags: added: xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sudo (Ubuntu) because there has been no activity for 60 days.]

Changed in sudo (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.