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

text/tabwriter: confusing panic backtrace #7117

Closed
josharian opened this issue Jan 13, 2014 · 1 comment
Closed

text/tabwriter: confusing panic backtrace #7117

josharian opened this issue Jan 13, 2014 · 1 comment

Comments

@josharian
Copy link
Contributor

What steps will reproduce the problem?

http://play.golang.org/p/pCybqtn361


What is the expected output? What do you see instead?

The output starts with:

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
    panic: interface conversion: interface is runtime.errorCString, not tabwriter.osError

This second panic message is a bit confusing. It looks a little like there is a bug in
tabwriter. More useful would be something like:

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
    panic: tabwriter: panic during Write


Please use labels and text to provide additional information.

This is a small, easy change. I'm happy to do it.
@josharian
Copy link
Contributor Author

Comment 1:

This issue was closed by revision d885aea.

Status changed to Fixed.

@josharian josharian added the fixed label Feb 4, 2014
@golang golang locked and limited conversation to collaborators Jun 25, 2016
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

2 participants