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

Jump to bottom

runtime: unexpected return pc using pprof on arm #6015

Closed
davecheney opened this issue Aug 2, 2013 · 6 comments
Closed

runtime: unexpected return pc using pprof on arm #6015

davecheney opened this issue Aug 2, 2013 · 6 comments
Labels
FrozenDueToAge
Milestone
Go1.2

Comments

@davecheney
Copy link
Contributor 

Enabling cpu profiling on a go program running on arm produces warnings from the runtime.

alarm(~/internet) % crawl -a 202 -b 114 -c 206 -d 221 
2013/08/02 04:00:05 profile: cpu profiling enabled, /tmp/profile167829215/cpu.pprof
runtime: unexpected return pc for runtime.parfordo called from 0xb3e75be8
2013/08/02 04:00:12 202.114.207.254:80: copied 6741 bytes, err <nil>
runtime: unexpected return pc for runtime.MCache_Refill called from 0x227fbc
2013/08/02 04:00:25 202.114.206.221:80: copied 122 bytes, err read tcp4
202.114.206.221:80: i/o timeout
runtime: unexpected return pc for net.(*Dialer).Dial called from 0x0

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

No warning messages from runtime.

Please use labels and text to provide additional information.

arch linux arm, linux/arm, pandaboard

alarm(~/go) % hg id
8b61a4ec6d1e+ tip
@davecheney
Copy link
Contributor Author

Comment 1:

This is a duplicate, sorry for the noise.

Status changed to Duplicate.

Merged into issue #6000.

@rsc
Copy link
Contributor

rsc commented Aug 2, 2013

Comment 2:

It's possible that this is a dup of 6000 but also possible that it's
something different. Let's leave them separate for now. If you can
reproduce the problem easily, please patch in CL 12362043, which should
print more information when it happens.
Thanks.
Russ

Status changed to Accepted.

@remyoudompheng
Copy link
Contributor

Comment 3:

Here is the output for crypto/des:
runtime: unexpected return pc for crypto/des.encryptBlock called from 0x7bf69d2e
crypto/des.feistel(0xf3ef917e, 0x0, 0x0, 0x7bf69d2e)
    /storage/remy/go/src/pkg/crypto/des/block.go:50 +0xb8
crypto/des.feistel(0x0, 0x25d1517c, 0xf3ef917e, 0xb)
    /storage/remy/go/src/pkg/crypto/des/block.go:43 +0x30
runtime: unexpected return pc for crypto/des.encryptBlock called from 0x7bf69d2e
crypto/des.encryptBlock(0x20cad0, 0x8, 0x8, 0x0, 0x4ee24, ...)
    /storage/remy/go/src/pkg/crypto/des/block.go:33 +0x78
runtime: unexpected return pc for crypto/des.encryptBlock called from 0x6d939aba
crypto/des.feistel(0x907a13f0, 0x0, 0x0, 0x6d939aba)
    /storage/remy/go/src/pkg/crypto/des/block.go:46 +0x80
crypto/des.feistel(0x0, 0x19df0b5c, 0x907a13f0, 0x8)
    /storage/remy/go/src/pkg/crypto/des/block.go:43 +0x30
runtime: unexpected return pc for crypto/des.encryptBlock called from 0x6d939aba
crypto/des.encryptBlock(0x20cad0, 0x8, 0x8, 0x0, 0x4ee24, ...)
    /storage/remy/go/src/pkg/crypto/des/block.go:33 +0x78
runtime: unexpected return pc for crypto/des.encryptBlock called from 0xa9b23234
crypto/des.feistel(0x5a5da34a, 0x0, 0x0, 0xa9b23234)
    /storage/remy/go/src/pkg/crypto/des/block.go:46 +0x80
crypto/des.feistel(0x0, 0x96e39712, 0x5a5da34a, 0xd)
    /storage/remy/go/src/pkg/crypto/des/block.go:43 +0x30

@remyoudompheng
Copy link
Contributor

Comment 4:

Something wrong happens in traceback_arm.c. For some reason, the traceback code uses
twice the same Func, increments sp twice by the same value and gets lost.

@dsymonds
Copy link
Contributor

Comment 5:

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

@rsc
Copy link
Contributor

rsc commented Sep 13, 2013

Comment 7:

This issue was closed by revision 439f939.

Status changed to Fixed.

@rsc rsc added this to the Go1.2 milestone Apr 14, 2015
@rsc rsc removed the go1.2 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.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.2
Development

No branches or pull requests
5 participants
@davecheney @dsymonds @rsc @remyoudompheng @gopherbot