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 info is not always present #257

Closed
IanBriggs opened this issue Apr 4, 2019 · 0 comments
Closed

Dwarf info is not always present #257

IanBriggs opened this issue Apr 4, 2019 · 0 comments
Labels
bug python Involves touching python code tests Involves touching tests

Comments

@IanBriggs
Copy link
Collaborator

Bug Report

Describe the problem
It is assumed in bisect that an object file used will always have DWARF info in it. This will not be true when the object file contains only constant data and no functions.

Suggested Fix
When no DWARF info is found check if the file has any functions. If no functions are found the file can be passed along with no need to record line numbers etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug python Involves touching python code tests Involves touching tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@IanBriggs @mikebentley15