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

cmd/link: GNU objdump for ppc64le binary errors: unable to get decompressed section .zdebug_abbrev #25948

Closed
laboger opened this issue Jun 18, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@laboger
Copy link
Contributor

commented Jun 18, 2018

What version of Go are you using (go version)?

tip

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

ppc64le

What did you do?

Used the GNU objdump on golang built binaries.

What did you expect to see?

The objdump output with no errors/warnings. I've used this for a long time without seeing these messages.

What did you see instead?

objdump: hello: unable to get decompressed section .zdebug_abbrev
objdump: hello: unable to get decompressed section .zdebug_line
objdump: hello: unable to get decompressed section .zdebug_frame
objdump: hello: unable to get decompressed section .zdebug_pubnames
objdump: hello: unable to get decompressed section .zdebug_pubtypes
objdump: hello: unable to get decompressed section .zdebug_info
objdump: hello: unable to get decompressed section .zdebug_loc
objdump: hello: unable to get decompressed section .zdebug_ranges

This happens on a simple hello program.
Seems to still generate the objdump OK.

@heschik

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2018

What version of objdump? 2.30 is perfectly content on my workstation when I do objdump --dwarf.

@laboger

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2018

This happens on an Ubuntu 16.04 with 2.26.1.
I can try some newer distros to see what happens.

@laboger

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2018

I see this on the 16.04 Ubuntu with 2.26.1

objdump -D hello > /dev/null
objdump: hello: unable to get decompressed section .zdebug_abbrev
objdump: hello: unable to get decompressed section .zdebug_line
objdump: hello: unable to get decompressed section .zdebug_frame
objdump: hello: unable to get decompressed section .zdebug_pubnames
objdump: hello: unable to get decompressed section .zdebug_pubtypes
objdump: hello: unable to get decompressed section .zdebug_info
objdump: hello: unable to get decompressed section .zdebug_loc
objdump: hello: unable to get decompressed section .zdebug_ranges

No messages with objdump --dwarf hello on that system.
I don't see any messages with objdump with either option on Ubuntu 18.04 with binutils 2.30.

@heschik

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2018

I doubt there's anything I can do, then. I could go find what changed, but odds are it was a bug in objdump and it's fixed, not anything we can work around short of rolling back DWARF compression.

@laboger

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2018

I mainly opened this for your awareness, and suppose it's OK that it works in a later objdump, which I didn't think to check.

@heschik

This comment has been minimized.

Copy link
Contributor

commented Jun 18, 2018

Cool. Thanks for the heads up.

@heschik heschik closed this Jun 18, 2018

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