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

net: RemoteAddr().String() crashes when getpeername failed #3721

Closed
gopherbot opened this issue Jun 10, 2012 · 7 comments

Comments

Projects
None yet
2 participants
@gopherbot
Copy link

commented Jun 10, 2012

by desnacked:

In "go version go1.0.1" the attached program fails with "invalid memory
address or nil pointer dereference" on the second Printf call.

Attachments:

  1. paste_173805 (356 bytes)
@mikioh

This comment has been minimized.

Copy link
Contributor

commented Jul 13, 2012

Comment 1:

Looks like Linux returns ENOTCONN when we call getpeername with raw IP socket.
BSD doesn't, not sure for Windows.

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Jul 18, 2012

Comment 2:

Owner changed to @mikioh.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Aug 23, 2012

Comment 3:

This issue was closed by revision 6cf77f2.

Status changed to Fixed.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Sep 18, 2012

Comment 4:

This issue was closed by revision e4389c0.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Sep 18, 2012

Comment 5:

Status changed to Accepted.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2013

Comment 6:

This issue was closed by revision 06cbe78.

Status changed to Fixed.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Mar 23, 2013

Comment 7:

This issue was closed by revision bfb32dc.

@golang golang locked and limited conversation to collaborators Jun 24, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.