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

x/net/websocket: server recovers from panics and then segfaults #2375

Closed
gopherbot opened this issue Oct 17, 2011 · 2 comments
Closed

x/net/websocket: server recovers from panics and then segfaults #2375

gopherbot opened this issue Oct 17, 2011 · 2 comments
Assignees
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Oct 17, 2011

by jacobsa@google.com:

What steps will reproduce the problem?

1. Download the attached file.
2. Run `6g panic.go && 6l panic.6 && ./6.out`.


What is the expected output?

The panic should be printed and then recovered from, and the server should continue
serving. I believe this is what happens when a panic happens in a regular old HTTP
handler.


What do you see instead?

See attached. The panic is recovered from, and then there is another panic due to an
invalid memory address or nil pointer dereference.


Which compiler are you using (5g, 6g, 8g, gccgo)?

6g


Which operating system are you using?

OS X 10.6.8


Which revision are you using?  (hg identify)

0445521cd154 tip


Please provide any additional information below.

Attachments:

  1. panic.go (489 bytes)
@adg
Copy link
Contributor

@adg adg commented Oct 17, 2011

Comment 1:

Owner changed to @adg.

Status changed to Started.

@adg
Copy link
Contributor

@adg adg commented Oct 17, 2011

Comment 2:

This issue was closed by revision 64471ae.

Status changed to Fixed.

@mikioh mikioh changed the title websocket server recovers from panics and then segfaults x/net/websocket: server recovers from panics and then segfaults Jul 30, 2015
@mikioh mikioh modified the milestone: Unreleased Jul 30, 2015
@golang golang locked and limited conversation to collaborators Aug 5, 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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.