You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
by jacobsa@google.com:
Attachments:
The text was updated successfully, but these errors were encountered: