kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled()

Bug #1758818 reported by marge
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled()

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: apport 2.20.8-0ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportLog:

ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 24 21:46:30 2018
ExecutablePath: /usr/share/apport/kernel_oops
InstallationDate: Installed on 2017-10-20 (156 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/kernel_oops 34436
ProcEnviron:
 PATH=(custom, no user)
 LANG=el_GR.UTF-8
 SHELL=/bin/false
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
SegvAnalysis:
 Segfault happened at: 0x4436c4: testb $0x40,0xa9(%rax)
 PC (0x004436c4) ok
 source "$0x40" ok
 destination "0xa9(%rax)" (0xdb2400ff242424cd) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 _PyGC_CollectIfEnabled ()
 ?? ()
Title: kernel_oops crashed with SIGSEGV in _PyGC_CollectIfEnabled()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
marge (mcmarat) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1758817, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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