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.

Sign up for GitHub

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

DWARF data is too new for us #139

Closed
aaronovz1 opened this issue Aug 17, 2018 · 1 comment · Fixed by #166
Closed

DWARF data is too new for us #139

aaronovz1 opened this issue Aug 17, 2018 · 1 comment · Fixed by #166

Comments

@aaronovz1
Copy link

I have a binary which has a mixture of compilation unit versions (2, 3, and 4). bloaty seems to only support up to 2 and will not partial process the binary if it has a mixture.

Any idea on when support for versions greater than 2 will happen?
@haberman
Copy link
Member

Oops, I thought I had updated everything for DWARF 4. But it looks like AddressRanges still only respects up to 2.

bloaty/src/dwarf.cc

Line 436 in feaca23

if (sizes_.dwarf_version() > 2) {

This should be an easy fix.

haberman added a commit to haberman/bloaty that referenced this issue Jun 5, 2019
@haberman
Fixed DWARF check to allow DWARF 4.
c313bb7 
Fixes google#139
@haberman haberman mentioned this issue Jun 5, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed DWARF check to allow DWARF 4. haberman/bloaty
2 participants
@haberman @aaronovz1