ndk-build: Use uid to limit logcat to the current application
#33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a port of: rust-mobile/xbuild#131 rust-mobile/xbuild#135 Having never really understood how Android Studio does it, I just stumbled upon this very new [stackoverflow answer] that has a rather beatiful solution to the current problems with `pidof`, without drawbacks. Pidof has always been flaky as it relies on the app to be running, which may either take some time or never happen if the app crashed before `pidof` is first run. This results in silly workarounds such as loops that induce extra delay and need to have an upper bound. And this `pid` changes every time the app is restarted, making it a tedious process that also doesn't react to manual app restarts on the device. Retrieving the `uid` via `pm list packages -U` on the other hand, and passing that to `logcat --uid` has the following advantages: - Always available immediately after the app has been installed, no need to check it in a loop (no extra delay); - Doesn't change after the app is (re!)installed, unless the user fully deletes and installs the app again; - Is resilient against app crashes because of that, and allows the user to see any error/crash related messages straight away; - Still includes logs printed by other system components that run or are invoked within an app, as before. The only downside is that `pm list package` possibly returns multiple packages if there is a substring match; for this reason the code searches for an explicit match in the output. [stackoverflow answer]: https://stackoverflow.com/a/76551835
MarijnS95
force-pushed
the
adb-logcat-uid
branch
from
5df5274
to
00d9dcc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10
This is a port of:
rust-mobile/xbuild#131
rust-mobile/xbuild#135
Having never really understood how Android Studio does it, I just stumbled upon this very new stackoverflow answer that has a rather beatiful solution to the current problems with
pidof, without drawbacks. Pidof has always been flaky as it relies on the app to be running, which may either take some time or never happen if the app crashed beforepidofis first run. This results in silly workarounds such as loops that induce extra delay and need to have an upper bound. And thispidchanges every time the app is restarted, making it a tedious process that also doesn't react to manual app restarts on the device. Retrieving theuidviapm list packages -Uon the other hand, and passing that tologcat --uidhas the following advantages:The only downside is that
pm list packagepossibly returns multiple packages if there is a substring match; for this reason the code searches for an explicit match in the output.