-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Support .a
and .rlib
static library files
#115
Comments
lib___.a
fileslib___.a
- archives of elf subfiles
lib___.a
- archives of elf subfileslib___.a
- archives of elf subfiles
Hey, thanks for creating the issue 👋🏼 Interesting feature request! Would you mind giving me more information about when this would be useful in real world scenario? I'm not that familiar with analyzing
I'm not sure if I understood this correctly, but where would you usually get an |
any compilation right before linking into an executable produces a bunch of .a files. A rust compilation produces |
lib___.a
- archives of elf subfileslib___.a
and lib___.rlib
- archives of elf .o
files
lib___.a
and lib___.rlib
- archives of elf .o
fileslib___.a
/ lib___.rlib
static libs containing .o
elf files
lib___.a
/ lib___.rlib
static libs containing .o
elf files.a
and .rlib
static library files
Thanks for the detailed explanation, I just got the chance to try this out and yeah, I think it would be nice to be able to run e.g. |
This one is tricky... My initial usecase was to inspect the exported symbols. Given a So perhaps these changes? Introduce component listJust like you suggested, you may want to have another screen when your input is an archive. That screen would list all archive components, and might offer some search capabilities that would look for things in all components. Once you hit I do not think you should support multiple files at the same time. There are enough tools for file management, e.g. yazi, and I'm not sure you want to duplicate that functionality. I see you currently allow more than one Maybe eventually you may want to add capability to search for symbols or strings or some other filtering capabilities - in which case yes, you might want to show a directory, listing only the binaries, and having some metadata next to each (as a table) - like some info from the file headers, string count, etc. Flatten
|
Is your feature request related to a problem? Please describe.
The .a static library is essentially an
ar
archive of elf files. I think the file reader could simply merge multiple elf files together when displaying, or some "context" or "stream" concept could be introduced to some screens, allowing switching between individual elf files in a single archive.To try it out locally, use
ar x <file>
to extract all .o files, which already can be viewed with binsiderDescribe the solution you'd like
Ability to view .a files
Describe alternatives you've considered
using
nm
andobjdump
to view file contentThe text was updated successfully, but these errors were encountered: