-
Notifications
You must be signed in to change notification settings - Fork 6
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
Move VirtAddrMap out of ElfEdit.Dynamic #18
Comments
I view that as a pretty simple data that is used to support the needs of parsing the dynamic section. It's it's useful for dynamic libraries and executables. I suppose it could be used for static executables as well, but not for object files. I'm not opposed to having it in a separate module though if that would be useful, and you want to submit a PR. |
Ah, I didn't think of it as specific to the parsing of the dynamic section because it is exported. Perhaps we should just not export it instead? Which would be best? |
I don't know what would be best. What's the goal of either change? |
I took a brief look to repage things in and it looks like it's only used to support the Android relocation entries in Macaw. Maybe there's some other way to refactor that code so we don't need this type, but I don't understand the goal. |
Sorry if my comments were unclear, let me back up a bit. At the moment,
among other things. Since Then you said:
So I thought my assumption (1) was flawed, and so instead of making this type and its operations more suitable for exposing through the API, maybe we should just not export it and keep it internal to |
This datatype isn't intrinsically related to dynamically-linked executables, so its placement in this module is a bit misleading.
The text was updated successfully, but these errors were encountered: