Skip to content
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

Update of libunwind to 1.8.0 has broken remote unwind #97343

Closed
janvorli opened this issue Jan 22, 2024 · 3 comments
Closed

Update of libunwind to 1.8.0 has broken remote unwind #97343

janvorli opened this issue Jan 22, 2024 · 3 comments
Assignees
Milestone

Comments

@janvorli
Copy link
Member

janvorli commented Jan 22, 2024

While running some debugging tests, I've hit a SIGSEGV in the unwinder during remote unwind. It stems from an incorrect change made in the libunwind in src/dwarf/Gget_proc_info_in_range.c in libunwind/libunwind#524. Reverting change in that file fixes the problem.

@janvorli janvorli added this to the 9.0.0 milestone Jan 22, 2024
@janvorli janvorli self-assigned this Jan 22, 2024
@ghost
Copy link

ghost commented Jan 22, 2024

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

Issue Details

While running some debugging tests, I've hit a SIGSEGV from the unwinder during remote unwind. It stems from an incorrect change made in the libunwind in src/dwarf/Gget_proc_info_in_range.c in libunwind/libunwind#524. Reverting change in that file fixes the problem.

Author: janvorli
Assignees: janvorli
Labels:

area-Diagnostics-coreclr

Milestone: 9.0.0

@AaronRobinsonMSFT
Copy link
Member

/cc @am11

@am11
Copy link
Member

am11 commented Feb 2, 2024

Fixed by #97813.

@am11 am11 closed this as completed Feb 2, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants