Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Fix dotnet-dump/createdump launch failure #25562

Merged
merged 1 commit into from
Jul 4, 2019
Merged

Conversation

mikem8361
Copy link
Member

On CentOS or OpenSUSE dotnet-dump collect fails but a
valid coredump is generated. The "prctl()" call is failing
that gives the child createdump process permission to ptrace
to the runtime process. On CentOS/OpenSUSE the PR_SET_PTRACER
option isn't supported and not needed.

Issue: dotnet/diagnostics#334

On CentOS or OpenSUSE dotnet-dump collect fails but a
valid coredump is generated. The "prctl()" call is failing
that gives the child createdump process permission to ptrace
to the runtime process. On CentOS/OpenSUSE the PR_SET_PTRACER
option isn't supported and not needed.

Issue: dotnet/diagnostics#334
@mikem8361 mikem8361 added this to the 3.0 milestone Jul 4, 2019
@mikem8361 mikem8361 requested a review from janvorli July 4, 2019 04:38
@mikem8361 mikem8361 self-assigned this Jul 4, 2019
@jkotas jkotas merged commit 036e426 into dotnet:master Jul 4, 2019
@mikem8361 mikem8361 deleted the createdump branch July 4, 2019 19:07
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
On CentOS or OpenSUSE dotnet-dump collect fails but a
valid coredump is generated. The "prctl()" call is failing
that gives the child createdump process permission to ptrace
to the runtime process. On CentOS/OpenSUSE the PR_SET_PTRACER
option isn't supported and not needed.

Issue: dotnet/diagnostics#334

Commit migrated from dotnet/coreclr@036e426
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants