You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applications may crash not only in java code and it would be very helpful if captured logs will have native backtraces (if any). At the moment SpoonDeviceLogger simply looks for a first message from instrumented application and then sticks to its pid to filter out all subsequent messages.
Unfortunately logs with native crashes come not from application process but from dedicated service that ptrace()'s crashed app (AFAIK they are debuggerd, crash_dump32, crash_dump_64. Actual one depends on Android version.). So simple pid comparison won't work.
The easies way would be to include all logs with DEBUG tag, as it is used by system for logging native crashes.
The text was updated successfully, but these errors were encountered:
Applications may crash not only in java code and it would be very helpful if captured logs will have native backtraces (if any). At the moment
SpoonDeviceLogger
simply looks for a first message from instrumented application and then sticks to its pid to filter out all subsequent messages.Unfortunately logs with native crashes come not from application process but from dedicated service that
ptrace()
's crashed app (AFAIK they aredebuggerd
,crash_dump32
,crash_dump_64
. Actual one depends on Android version.). So simple pid comparison won't work.The easies way would be to include all logs with
DEBUG
tag, as it is used by system for logging native crashes.The text was updated successfully, but these errors were encountered: