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

objdump: does not work on windows #4841

Closed
gopherbot opened this issue Feb 18, 2013 · 5 comments
Closed

objdump: does not work on windows #4841

gopherbot opened this issue Feb 18, 2013 · 5 comments
Milestone

Comments

@gopherbot
Copy link

by Vova616:

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1.use objdump in general or in pprof on windows
2.
3.

What is the expected output?
Work

What do you see instead?
Crash on 1.0.3 and Internal fatal error on tip.

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

Which operating system are you using?
Windows 7 64bit

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

Please provide any additional information below.
Looks like machdata is nil because machbytype(fhdr.type) could not find machines with
the given type. (the given type on windows is FWINPE while there is no machine with this
type in Machines array in setmach.c)
@alexbrainman
Copy link
Member

Comment 1:

Yep.
# pwd                                         
/root/go/src/pkg/net                             
# GOOS=windows go test -c                     
# go tool nm net.test.exe | head              
  40eea0 t BestFit                                    
  4138b0 t LockOSThread                               
  4054c0 t LostProfileData                            
  40a2b0 t MCentral_Free                              
  40a570 t MCentral_Grow                              
  40ee50 t MHeap_AllocLarge                           
  40eba0 t MHeap_AllocLocked                          
  40f210 t MHeap_FreeLocked                           
  40ef10 t MHeap_Grow                                 
  41a300 t MProf_GC                                   
go tool nm: signal: broken pipe                       
# go tool objdump ./net.test.exe 40eea0 40eeff
go tool objdump: signal: segmentation fault           
#

Labels changed: added compilerbug, os-windows.

Status changed to Accepted.

@alexbrainman
Copy link
Member

Comment 2:

https://golang.org/cl/7405050/

Status changed to Started.

@alexbrainman
Copy link
Member

Comment 3:

This issue was closed by revision e72d1a9.

Status changed to Fixed.

@alexbrainman
Copy link
Member

Comment 4:

Unfortunately, it is still broken on amd64. Here is more fixes
https://golang.org/cl/7475046/.

Status changed to Started.

@alexbrainman
Copy link
Member

Comment 5:

This issue was closed by revision e44f42e.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1maybe 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.
Projects
None yet
Development

No branches or pull requests

3 participants