upstart crashed with SIGSEGV

[Mike Durham]

nothing to add

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: upstart-bin 1.13.2-0ubuntu7
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Feb 19 15:17:37 2015
ExecutablePath: /sbin/upstart
InstallationDate: Installed on 2014-10-25 (117 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
ProcCmdline: /sbin/init
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdline: root=LABEL=P1 ro splash
SegvAnalysis:
 Segfault happened at: 0x104d0: mov %edi,0x18(%esi)
 PC (0x000104d0) not located in a known VMA region (needed executable region)!
 source "%edi" ok
 destination "0x18(%esi)" (0x0000404a) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing unknown VMA
 writing NULL VMA
Signal: 11
SourcePackage: upstart
Stacktrace:
 #0 0x000104d0 in ?? ()
 No symbol table info available.
 #1 0x0001012d in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: upstart crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSystemVersion: init (upstart 1.13.2)
UserGroups:

modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
modified.conffile..etc.sysctl.d.10.ptrace.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-10-27T19:52:08.905081
mtime.conffile..etc.sysctl.d.10.ptrace.conf: 2014-11-07T10:26:33.901893

[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 #1419393, 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.