Do you have interest in different output formats?

[jamesmunns]

Hey! Thanks for sharing the awesome tool!

I typically work with microcontrollers, and thought it might be useful to have a similar view to what you are rendering here, but slightly less oriented towards looking at the elf file itself, and more oriented to "what ends up on the microcontroller".

I have a little mockup of what I mean in this twitter post, let me know if this is something you would be open to having as an option for elfcat, or if it would be better as a separate tool.

Thanks again!

[rbakbashev]

That's a really cool mockup. I can say that plans I have regarding "Visualization of virtual memory mappings" mentioned in TODO in readme closely look like what you have. Except that there's no distinction between RAM and ROM[1]: it would show loadable segments and sections just put on a 1-dimensional virtual memory axis.

There's actually an uncommitted prototype of this, it's just looks very bad: the linear scale is incomprehensible, and other logarithmic, etc. need careful consideration with regards to overlaps and so on. So, I postponed this feature.

[1]: I'm guessing if we put labels (.data, .text, and so on) then this would look better. Thanks for that design inspiration. After that, to look like your mockup we would need symbolization, etc. Not sure how doable it would be.

[jamesmunns]

Hey thanks! I think re: symbolization, it looks like cargo-bloat uses a library called binfarce to do this in a minimal way (vs bringing in all of goblin or similar).

I definitely think this will end up "sparse", e.g. for most Arm MCUs, .text (and other ROM-ish data) lives at 0x0000_0000, and .data (and other RAM-ish data) lives at 0x2000_0000.

Let me know if I can help test or anything, or chat about what might look good (or not!)