Skip to content

Fix dump creation on MacOS Ventura #79356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 7, 2022
Merged

Conversation

mikem8361
Copy link
Contributor

@mikem8361 mikem8361 commented Dec 7, 2022

Use the task_info(TASK_DYLD_INFO) API to get the dylinker info instead of enumerating all the memory regions. This works on Ventura and simplifies the module enumeration quite a bit.

This greatly affects VS4Mac on Ventura.

Issue: #79355

Use the task_info(TASK_DYLD_INFO) API to get the dylinker info instead of
enumerating all the memory regions. This works on Ventura and simplifies
the module enumeration quite a bit.
@mikem8361 mikem8361 requested a review from hoyosjs December 7, 2022 18:27
@mikem8361 mikem8361 self-assigned this Dec 7, 2022
@ghost
Copy link

ghost commented Dec 7, 2022

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

Use the task_info(TASK_DYLD_INFO) API to get the dylinker info instead of enumerating all the memory regions. This works on Ventura and simplifies the module enumeration quite a bit.

This greatly affects VS4Mac which 35% of their crash reports are on Ventura.

Issue: #79355

Author: mikem8361
Assignees: mikem8361
Labels:

area-Diagnostics-coreclr

Milestone: -

@mikem8361
Copy link
Contributor Author

/cc: @kdubau, @sgmunn

@tommcdon
Copy link
Member

tommcdon commented Dec 7, 2022

cc @janvorli in case some extra review would be useful

@hoyosjs
Copy link
Member

hoyosjs commented Dec 7, 2022

/backport to release/6.0

@hoyosjs
Copy link
Member

hoyosjs commented Dec 7, 2022

/backport to release/7.0

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/3642524580

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3642525290

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

@hoyosjs backporting to release/6.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Fix dump creation on MacOS Ventura
Using index info to reconstruct a base tree...
M	src/coreclr/debug/createdump/crashinfo.h
M	src/coreclr/debug/createdump/crashinfomac.cpp
Falling back to patching base and 3-way merge...
Auto-merging src/coreclr/debug/createdump/crashinfomac.cpp
CONFLICT (content): Merge conflict in src/coreclr/debug/createdump/crashinfomac.cpp
Auto-merging src/coreclr/debug/createdump/crashinfo.h
CONFLICT (content): Merge conflict in src/coreclr/debug/createdump/crashinfo.h
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix dump creation on MacOS Ventura
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2022

@hoyosjs an error occurred while backporting to release/6.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@mikem8361 mikem8361 merged commit a10bfec into dotnet:main Dec 7, 2022
@mikem8361 mikem8361 deleted the venturafix branch December 7, 2022 23:17
@ghost ghost locked as resolved and limited conversation to collaborators Jan 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants