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

Jump to bottom

runtime: print SIGSEGV/SIGBUS fault address from system stack #60894

Closed
prattmic opened this issue Jun 20, 2023 · 1 comment
Closed

runtime: print SIGSEGV/SIGBUS fault address from system stack #60894

prattmic opened this issue Jun 20, 2023 · 1 comment
Assignees
@prattmic
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.22

Comments

@prattmic
Copy link
Member

Normally sigpanic is responsible for printing the fault address of a SIGSEGV / SIGBUS, but when a signal occurs on the system stack, we convert to a throw. Thus the signal print occurs in fatalsignal, which does not attempt to print the fault address.

cc @golang/runtime
@prattmic prattmic added the NeedsFix The path to resolution is known, but the work has not been done. label Jun 20, 2023
@prattmic prattmic added this to the Backlog milestone Jun 20, 2023
@prattmic prattmic self-assigned this Jun 20, 2023
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jun 20, 2023
@gopherbot
Copy link

Change https://go.dev/cl/504635 mentions this issue: runtime: print fault addr in fatalsignal

@mknyszek mknyszek modified the milestones: Backlog, Go1.22 Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prattmic prattmic

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done.
Projects
Go Compiler / Runtime
Status: Done
Milestone
Go1.22
Development

No branches or pull requests
3 participants
@mknyszek @prattmic @gopherbot