Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Show info from crash_dump process on native crashes #7

Open
flimberger opened this issue Mar 16, 2020 · 0 comments
Open

Show info from crash_dump process on native crashes #7

flimberger opened this issue Mar 16, 2020 · 0 comments
Assignees
@flimberger
Labels
enhancement New feature or request

Comments

@flimberger
Copy link
Owner

To improve experience during native development, the information from the crash_dump service should be printed, which usually includes a stack trace. This information is discarded if alogview filters for package names, which is unfortunate. Since alogview already checks for messages from the ActivityManager, it should be possible to do the same for the crash_dump process.
@flimberger flimberger added the enhancement New feature or request label Mar 16, 2020
@flimberger flimberger self-assigned this Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flimberger flimberger

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@flimberger