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 signal name, not number, for fatal signal error #13969

Closed
perillo opened this issue Jan 15, 2016 · 4 comments
Closed

runtime: print signal name, not number, for fatal signal error #13969

perillo opened this issue Jan 15, 2016 · 4 comments
Labels
FrozenDueToAge
Milestone
Go1.7

Comments

@perillo
Copy link
Contributor

perillo commented Jan 15, 2016

Currently, after a fatal error caused by an unexpected signal during runtime execution, the runtime prints, as an example:
[signal 0xb code=0x80 addr=0x0 pc=0x406230]

Since the runtime knows about signal numbers, it should print the signal name instead of the signal number.

See https://groups.google.com/forum/#!topic/golang-nuts/_FYWG3oU6X8
@ianlancetaylor ianlancetaylor changed the title Make fatal error reports more user friendly runtime: print signal name, not number, for fatal signal error Jan 15, 2016
@ianlancetaylor ianlancetaylor added this to the Go1.7 milestone Jan 15, 2016
@odeke-em
Copy link
Member

odeke-em commented May 4, 2016

@ianlancetaylor I just wanted to get your confirmation that it is okay to fix this or does anyone think this breaks compatibility with older versions of Go? I am asking because I'd like to spin up a CL for this.

@ianlancetaylor
Copy link
Contributor

@odeke-em It is OK to fix this. Thanks.

@odeke-em
Copy link
Member

odeke-em commented May 4, 2016

Cool, thanks for the ACK.

@gopherbot
Copy link

CL https://golang.org/cl/22753 mentions this issue.

@golang golang locked and limited conversation to collaborators May 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.7
Development

No branches or pull requests
4 participants
@ianlancetaylor @odeke-em @perillo @gopherbot