Start debuggerd as soon as logd is up.
Makes debugging early boot crashes easier. Bug: http://b/26918597 Change-Id: I5bb883f1350ea5f7a545cb0e9f1034ecfcf47cdb
This commit is contained in:
parent
650f6809a3
commit
2f74a5dae5
|
@ -1,4 +1,3 @@
|
|||
service debuggerd /system/bin/debuggerd
|
||||
class main
|
||||
group root readproc
|
||||
writepid /dev/cpuset/system-background/tasks
|
||||
|
|
|
@ -1,4 +1,3 @@
|
|||
service debuggerd64 /system/bin/debuggerd64
|
||||
class main
|
||||
group root readproc
|
||||
writepid /dev/cpuset/system-background/tasks
|
||||
|
|
|
@ -297,8 +297,12 @@ on post-fs-data
|
|||
# We restorecon /data in case the userdata partition has been reset.
|
||||
restorecon /data
|
||||
|
||||
# Make sure we have the device encryption key
|
||||
# Start logd, then start debuggerd to make debugging early-boot crashes easier.
|
||||
start logd
|
||||
start debuggerd
|
||||
start debuggerd64
|
||||
|
||||
# Make sure we have the device encryption key.
|
||||
start vold
|
||||
installkey /data
|
||||
|
||||
|
|
Loading…
Reference in New Issue