diff options
| author | Tom Cherry <tomcherry@google.com> | 2017-08-22 16:15:26 -0700 |
|---|---|---|
| committer | Tom Cherry <tomcherry@google.com> | 2017-08-23 11:05:37 -0700 |
| commit | 68f2a4614518468f1320ad3e62a6db554e509fb1 (patch) | |
| tree | 379a26958c3c70d672bae20d0a099c9a82ed98a3 /trusty | |
| parent | 76af7e6a0c4ce7759e6cc5994b5496ddb09035ee (diff) | |
| download | core-68f2a4614518468f1320ad3e62a6db554e509fb1.tar.gz core-68f2a4614518468f1320ad3e62a6db554e509fb1.tar.bz2 core-68f2a4614518468f1320ad3e62a6db554e509fb1.zip | |
init: enable error reporting of builtin functions
Enable error reporting when builtin functions fail. These errors are
now reported with full context including the source file and line
number, e.g.
init: Command 'write /sys/module/subsystem_restart/parameters/enable_debug ${persist.sys.ssr.enable_debug}' action=early-boot (/init.bullhead.rc:84) took 0ms and failed: cannot expand '${persist.sys.ssr.enable_debug}'
There are two small caveats:
1) There are nearly 200 reports of builtins failure due to "No such
file or directory". Many of these are due to legacy paths included
in rootdir/init.rc. Until they are cleaned up, reporting of these
failures is disabled.
2) Similarly, symlink is often used to create backwards compatible
symlinks. By their very nature, these calls are expected to fail
on newer systems that do already use the new path. Due to this,
failures of symlink due to EEXIST are not reported.
Bug: 38038887
Test: boot bullhead, only see true errors reported from builtins.
Change-Id: I316c13e3adc992cacc6d79ffee987adc8738fca0
Diffstat (limited to 'trusty')
0 files changed, 0 insertions, 0 deletions