dpkg crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
gfhg
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: dpkg 1.18.24ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 21 20:48:57 2017
ExecutablePath: /usr/bin/dpkg
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/dpkg --status-fd 35 --no-triggers --unpack --auto-deconfigure /var/cache/
SegvAnalysis:
Segfault happened at: 0x5588874144c0: movl $0x0,0x28(%rax)
PC (0x5588874144c0) ok
source "$0x0" ok
destination "0x28(%rax)" (0x4000000028) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
__libc_start_main (main=0x5588874
Title: dpkg crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #359127, 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.