[Android] Add error code to the assert error message #80423
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
|
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue DetailsThere is a report of a crash when JNI
|
|
/azp run runtime-android |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…ble-to-attach-thread-crash
grendello
approved these changes
Jan 16, 2023
mkhamoyan
approved these changes
Jan 16, 2023
akoeplinger
approved these changes
Jan 16, 2023
This comment was marked as duplicate.
This comment was marked as duplicate.
|
/backport to release/7.0 |
|
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3931955733 |
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/3932028555 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There is a report of a crash when JNI
AttachCurrentThreadAsDaemonmethod is called (#79395). The logs don't contain any relevant information so it's hard to diagnose the root of the problem. We should output the error code returned fromAttachCurrentThreadAsDaemonto make diagnosing the error easier.