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.

Sign up for GitHub

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

Jump to bottom

Figure out a way to get source location in ManagedCallFrameSymbolicator #24

Open
alexrp opened this issue Jul 13, 2022 · 0 comments
Open

Figure out a way to get source location in ManagedCallFrameSymbolicator #24

alexrp opened this issue Jul 13, 2022 · 0 comments
Labels
area: diagnostics Issues related to the call stack tracing APIs. state: approved Enhancements and tasks that have been approved.
Milestone
Future

Comments

@alexrp
Copy link
Member

alexrp commented Jul 13, 2022

ruptura/src/memory/Diagnostics/ManagedCallFrameSymbolicator.cs

Lines 54 to 55 in 7016826

// TODO: Figure out a way to get source location information.
return new((void*)method.MethodHandle.GetFunctionPointer(), sb.ToString(), null, 0, 0);

It does not seem like there's going to be an easy way to do this.
@alexrp alexrp added state: approved Enhancements and tasks that have been approved. type: feature area: hooking Issues related to the function hooking APIs. labels Jul 13, 2022
@alexrp alexrp added this to the v2.0 milestone Jul 13, 2022
@alexrp alexrp self-assigned this Jul 13, 2022
@alexrp alexrp modified the milestones: v2.0, v3.0 Jul 23, 2022
@alexrp alexrp added area: diagnostics Issues related to the call stack tracing APIs. and removed area: hooking Issues related to the function hooking APIs. labels Jul 28, 2022
@alexrp alexrp removed their assignment Jan 27, 2024
@alexrp alexrp modified the milestones: v4.0, Future Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: diagnostics Issues related to the call stack tracing APIs. state: approved Enhancements and tasks that have been approved.
Milestone
Future
Development

No branches or pull requests
1 participant
@alexrp