Fix potential deadlock in bsg_kscrw_i_writeThread() #1453
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Fix a potential deadlock when capturing the crashed thread's name - see #1406
Design
bsg_ksmachgetThreadName()
usespthread_from_mach_thread_np()
which acquires a lock and is therefore unsafe to call from a crash handler.Changeset
Replaces use of
bsg_ksmachgetThreadName()
withpthread_getname_np(pthread_self(), ...)
to avoid potential deadlock.Testing
Thread name capture is verified for C++ exceptions and NSExceptions since #1406