Skip to content

Change macOS activatin injection failure handling - #59045

Merged
janvorli merged 1 commit into
dotnet:mainfrom
janvorli:change-osx-pthread-kill-failure-handling
Sep 14, 2021
Merged

Change macOS activatin injection failure handling#59045
janvorli merged 1 commit into
dotnet:mainfrom
janvorli:change-osx-pthread-kill-failure-handling

Conversation

@janvorli

@janvorlijanvorli commented Sep 13, 2021

Copy link
Copy Markdown
Member

The pthread_kill can fail with ENOTSUP on macOS when the target thread
is a dispatch queue thread. Instead of aborting the process, it is
better to fail to inject the activation and rely on return address
hijacking and other means of syncing with GC.

Close#58111

The pthread_kill can fail with ENOTSUP on macOS when the target thread
is a dispatch queue thread. Instead of aborting the process, it is
better to fail to inject the activation and rely on return address
hijacking and other means of syncing with GC.
@janvorlijanvorli added the area-PAL-coreclr only for closed issues label Sep 13, 2021
@janvorlijanvorli added this to the 6.0.0 milestone Sep 13, 2021
@janvorlijanvorli self-assigned this Sep 13, 2021

@jkotasjkotas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@janvorli
janvorli merged commit dc678c8 into dotnet:mainSep 14, 2021
@janvorli
janvorli deleted the change-osx-pthread-kill-failure-handling branch September 14, 2021 20:00
@ghostghost locked as resolved and limited conversation to collaborators Nov 3, 2021
@janvorli

Copy link
Copy Markdown
MemberAuthor

/backport to release/6.0

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-PAL-coreclronly for closed issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[MacOS] EXC_CRASH (SIGABRT) when GC occurs from within a callback made out of an Dispatch queue: com.apple.root.default-qos thread

2 participants

@janvorli@jkotas