Support .a and .rlib static library files

[nyurik]

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 binsider

Describe the solution you'd like

Ability to view .a files

Describe alternatives you've considered

using nm and objdump to view file content

[orhun]

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 .a files (or with .a files for that matter).

To try it out locally, use ar x to extract all .o files, which already can be viewed with binsider

I'm not sure if I understood this correctly, but where would you usually get an .a file? Just wanted to try it out for myself :)

[nyurik]

any compilation right before linking into an executable produces a bunch of .a files. A rust compilation produces .rlib files - which are almost identical to .a (they have some extra metadata i heard). So to try it out, simply look at your target/ dir, e.g. target/debug/libbinsider.rlib - and run ar x target/debug/libbinsider.rlib and do cargo run <one of the extracted files.o>