Riccardo Schirone

@GustavoLCR did you implement this?

BTW, some code uses `CSNEXT` because acr/make defines that, however I think it is wrong and we should just use `CS_API_MAJOR`/`CS_API_MINOR` as usual.

> Currently Rizin uses `sdb_fmt` function, often as an argument that could cause a leak I think this is not true. `sdb_fmt` gets string from the stack, so they cannot...

What version of rizin are you using? This is what get with rizin from `dev` branch. ``` ./build/binrz/rizin/rizin ./arm_sample -- The more 'a' you add after 'aa' the more analysis...

``` ┌ fcn.00010b3c (); │ 0x00010b3c push {r4, lr} │ 0x00010b40 mov r0, 1 │ 0x00010b44 bl fcn.0001308c ;[1] │ 0x00010b48 ldr r4, [0x00010b78] ; [0x10b78:4]=0x26420 │ 0x00010b4c ldr r3,...

Dropping here some thoughts on what could be done (though @wargio might know better): - change rz_bin_file_strings from `RZ_API RZ_OWN RzList /**/ *rz_bin_file_strings(RZ_NONNULL RzBinFile *bf, size_t min_length, bool raw_strings)` to...

Still, it should be possible for users to select a

I agree. I think grep syntax should be completely moved and handled by the parser. Right now almost everything after `~` is passed to rz_cons_grep, which does not support many...

> @ret2libc in fact, now with `:` modifiers, it makes sense to maybe use something like `:json` or similar instead of `~{}` for pretty-printing. What do you think? I think...

> We should move `grep` feature out of the RzCons and to the RzCore. I'm not sure.... I think there are a lot of things you need to do inside...