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

cmd/go: report program name in execution failure #6823

Closed
rsc opened this issue Nov 23, 2013 · 8 comments
Closed

cmd/go: report program name in execution failure #6823

rsc opened this issue Nov 23, 2013 · 8 comments
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Nov 23, 2013

What steps will reproduce the problem?
1. Make, say, 5l crash in ordinary operation.
2. go build hello.go

$ go build ~/hello.go
go build command-line-arguments: signal: segmentation fault
$ 

There's no indication that the program that crashed was 5l.

This applies to all tools run, not just 5l.
@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 1:

Labels changed: added release-go1.3.

@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 2:

Labels changed: removed go1.3.

@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 3:

Labels changed: added repo-main.

@gopherbot
Copy link

Comment 4:

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

@bradfitz
Copy link
Contributor

Comment 5:

Doesn't seem critical and Russ doesn't know what he wants (per
https://golang.org/cl/89190044) so lowering priority. Likely punt to Go1.4.

Labels changed: added release-go1.3maybe, removed release-go1.3.

@rsc
Copy link
Contributor Author

rsc commented May 27, 2014

Comment 6:

Labels changed: added release-go1.4, removed release-go1.3maybe.

@gopherbot
Copy link

Comment 7:

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

@rsc
Copy link
Contributor Author

rsc commented Sep 26, 2014

Comment 8:

This issue was closed by revision 13a2c1c.

Status changed to Fixed.

@rsc rsc added fixed labels Sep 26, 2014
@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jun 25, 2018
Fix by atom (from CL 89190044), comment and test by me.

Fixes golang#6823.

LGTM=crawshaw
R=golang-codereviews, crawshaw
CC=0xe2.0x9a.0x9b, adg, golang-codereviews, iant, r
https://golang.org/cl/148180043
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jun 26, 2018
Fix by atom (from CL 89190044), comment and test by me.

Fixes golang#6823.

LGTM=crawshaw
R=golang-codereviews, crawshaw
CC=0xe2.0x9a.0x9b, adg, golang-codereviews, iant, r
https://golang.org/cl/148180043
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jul 9, 2018
Fix by atom (from CL 89190044), comment and test by me.

Fixes golang#6823.

LGTM=crawshaw
R=golang-codereviews, crawshaw
CC=0xe2.0x9a.0x9b, adg, golang-codereviews, iant, r
https://golang.org/cl/148180043
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jul 30, 2018
Fix by atom (from CL 89190044), comment and test by me.

Fixes golang#6823.

LGTM=crawshaw
R=golang-codereviews, crawshaw
CC=0xe2.0x9a.0x9b, adg, golang-codereviews, iant, r
https://golang.org/cl/148180043
This issue was closed.
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