auplink crashed with SIGSEGV in ftw_startup()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aufs-tools (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Crash happens at the laptop boot time, right I after signing in to the use account. I did not do any special actions to cause it.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: aufs-tools 1:3.2+20130722-
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 11 15:44:23 2016
Dependencies:
gcc-6-base 6-20160405-0ubuntu2
libc6 2.23-0ubuntu2
libgcc1 1:6-20160405-
ExecutablePath: /sbin/auplink
InstallationDate: Installed on 2016-04-03 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: auplink /var/lib/
SegvAnalysis:
Segfault happened at: 0x7f658ff64419 <ftw_startup+105>: callq 0x7f658fef9bd0 <__memset_sse2>
PC (0x7f658ff64419) ok
source "0x7f658fef9bd0" (0x7f658fef9bd0) ok
destination "(%rsp)" (0x7ffe8dbd27f0) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: aufs-tools
StacktraceTop:
ftw_startup (dir=0x137e010 "/var/lib/
?? ()
?? ()
__libc_start_main (main=0x401266, argc=3, argv=0x7ffe8e3d
?? ()
Title: auplink crashed with SIGSEGV in ftw_startup()
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 #1545265, 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.