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

Consider switching to goblin for ELF support #586

Open
danielocfb opened this issue Apr 2, 2024 · 1 comment
Open

Consider switching to goblin for ELF support #586

danielocfb opened this issue Apr 2, 2024 · 1 comment

Comments

@danielocfb
Copy link
Collaborator

danielocfb commented Apr 2, 2024

We may want to consider switching to using the goblin crate for our ELF parsing needs. As per my understanding it is stable and used in many contexts. Doing so could also help with issues such as #64 and #53. The reasons for rolling our own ELF parser were somewhere along the lines of performance, but never backed by data to the best of my knowledge.

@danielocfb danielocfb changed the title Consider switching to gimli for ELF support Consider switching to goblin for ELF support Apr 8, 2024
@libbpf libbpf deleted a comment from danielocfb Dec 13, 2024
@d-e-s-o
Copy link
Collaborator

d-e-s-o commented Dec 13, 2024

I am not super eager to embark on this switch, as our ELF parser seems sufficiently mature at this point. That being said, I think the switch to goblin could help with two things:

  • PE support (which apparently it has out of the box); it's still a question whether that would be useful on its own or whether we'd need logic to work with some debug format on top of that to really provide value-add
  • non-native endian handling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants