Skip to content

runtime: incorrect backtrace for blocked goroutine #4150

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

Closed
gpaul opened this issue Sep 25, 2012 · 4 comments
Closed

runtime: incorrect backtrace for blocked goroutine #4150

gpaul opened this issue Sep 25, 2012 · 4 comments
Labels
FrozenDueToAge Suggested Issues that may be good for new contributors looking for work to do.
Milestone

Comments

@gpaul
Copy link
Contributor

gpaul commented Sep 25, 2012

What steps will reproduce the problem?
1. go run bad_stack.go
2. netstat -na | grep pprof
3. echo -e "GET /debug/pprof/goroutine?debug=1 HTTP/1.0\n" | socat STDIO
ABSTRACT:/pprof/<pid>
4. kill -s QUIT <pid>

What is the expected output?
The pprof stack should put the foo() routine at the select{}, but puts it at the next
line instead.

What do you see instead?

// Goroutine profile contains this:
1 @ 0x41205c 0x4120c6 0x403770 0x403858 0x400cab 0x410da0
#   0x400cab    main.foo+0x5b   /home/gustav/bad_stack2.go:27

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

Which operating system are you using?
Linux 3.4.7-1.fc16.x86_64 #1 SMP Mon Jul 30 16:37:23 UTC 2012 x86_64 x86_64 x86_64
GNU/Linux

Which version are you using?  (run 'go version')
edge

Please provide any additional information below.

Attachments:

  1. bad_stack2.go (716 bytes)
@rsc
Copy link
Contributor

rsc commented Oct 6, 2012

Comment 1:

I tried to reproduce this on my Mac and could not. I have not tried on Linux yet.

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

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Dec 10, 2012

Comment 2:

Labels changed: added size-m.

@rsc
Copy link
Contributor

rsc commented Dec 10, 2012

Comment 3:

Labels changed: added suggested.

@rsc
Copy link
Contributor

rsc commented Feb 15, 2013

Comment 4:

This issue was closed by revision 318309a.

Status changed to Fixed.

@gpaul gpaul added fixed Suggested Issues that may be good for new contributors looking for work to do. labels Feb 15, 2013
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@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.
Labels
FrozenDueToAge Suggested Issues that may be good for new contributors looking for work to do.
Projects
None yet
Development

No branches or pull requests

3 participants