Cutter: Support Intel Hex as input file format

Created on 16 May 2019  Â·  8Comments  Â·  Source: rizinorg/cutter

Is your feature request related to a problem? Please describe.

I can't open file in Intel Hex format with Cutter. The file:// prefix in IO at startup window can't be changed. The file format must be specified for Radar2 as ihex://, so that it opens it as Intel Hex.

изображение

Describe the solution you'd like

The IO prefix can be editable. Or it finally can be extended with all supported options.

Describe alternatives you've considered


Trying to use r2 in cli mode.

Additional context


Sorry for my English.

BUG

All 8 comments

Hello,
Interesting issue as hex input file format is already supported! The funny thing is that the dropdown menu seems hidden, there are actually many more IO available, including ihex://.
Thanks for reporting this, can you give more details on what your OS is, what version of Cutter are you using, etc.? If you start it from terminal, maybe can you see some error messages?

Oh, I’m sorry. I forgot for system info.
I use Windows 10 1809 x86 64bit and Cutter Version 1.8.1 Using r2-3.4.1 from the github releases page.
Terminal is empty. Also the RIO tab under the radare2 plugin information window is empty if it is matter. There was only file:// item in that title window.

Offtopic: when I start cutter -h a help in window is badly formatted:
изображение

I am getting the same on Linux with Cutter I compiled from master and r2 which gets included as submodule built using ./sys/user.sh.

Looks like json field names in CutterCore::getRIOPluginDescriptions are slighltly different from ones I see when running oLj. Changing them to match helped.

There is also now an uris field which we should probably use instead of name as they don't necessarily match. A plugin can also have multiple uris with different behavior.

Yep indeed, I remember asking for that in radare2.

good catch @karliss

Was this page helpful?
0 / 5 - 0 ratings