Skip to content

Conversation

@marti4d
Copy link
Collaborator

@marti4d marti4d commented Dec 25, 2025

When Android Isolated Process is enabled, every process exists in its own ephemeral UID and SELinux context. That will essentially block ptrace() and I/O to /proc/<pid>, which means minidump-writer currently can't be used to dump Isolated Processes.

This change refactors existing code to do all forbidden operations through a trait, ProcessInspector, that currently only has one implementation - DirectInspector - which calls the APIs directly (like the current implementation does).

In the next change, we will add another implementation of ProcessInspector - remote::InspectorInvoker and its other half remote::InspectorExecutor - That will allow minidump-writer to send ptrace() and /proc/<pid> I/O requests to a remote process that does have the required permissions.

Fixes #166

When Android Isolated Process is enabled, every process exists in its
own ephemeral UID and SELinux context. That will essentially block
`ptrace()` and I/O to `/proc/<pid>`, which means minidump-writer
currently can't be used to dump Isolated Processes.

This change refactors existing code to do all forbidden operations
through a trait, `ProcessInspector`, that currently only has one
implementation - `DirectInspector` - which calls the APIs directly
(like the current implementation does).

In the next change, we will add another implementation of
`ProcessInspector` - `remote::InspectorInvoker` and its other half
`remote::InspectorExecutor` - That will allow minidump-writer to
send `ptrace()` and `/proc/<pid>` I/O requests to a remote process
that does have the required permissions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Minidump-Writer won't work in an Android Isolated Process

1 participant