The only things I actually miss is a simple 'math' engine to 's102+33'
(for example)
and a way to type multiple commands in a line (using the ';'
separator?), maybe
comments with '#' and not much more. A manpage would be good to have.
If you think that there's something I miss ping me :) i'll love to hear
and discuss
tips and ideas for it. Keeping it minimal means constant refactoring and
testing,
this way (ala suckless) give us a small core, very tested and clean code.
Those are the development guidelines for RED and I think they can help
us to view
the software from a new perspective.
All the scripting support and so one should be done externally, like the
support
for flags and the rest of complicated stuff.
I don't want to put much complexity on red. It doesnt tries to replace
radare at all :)
Robin Vossen wrote:
I kinda like this tool...
Its really slim, the code is really easy.
And well it works.
- Robin
2009/7/11 pancake <[email protected] <mailto:[email protected]>>
I have been silently developing some applications these days :)
This mail is to present one of them: 'red'.
RED aims to be a minimalistic version of radare. It is done in less
than 500 lines of code. And it aims to keep the source as simple
and minimal as possible.
Today the 0.1 was released. the source can be downloaded at:
http://radare.org/get/red-0.1.tar.gz
And the w32 binary (using w32 IO) in:
http://radare.org/get/red.exe
The visual mode is actually implemented in a stupid shellscript of
50 LOC that get keys and translates them into red commands.
Actually, on debian systems there's a binary named 'red' that is
a symlink against 'ed' and stands for 'restricted ed'.. i dont plan
to change the name, and i dont really know anybody using GNU
'ed' or 'red' nowadays.
The IO can be easily replaced to provide another backend like
'rap' protocol for remote connections, debugger backend, etc..
But I will keep this task to external projects or preloaded libraries,
this will stop making red that simple.
I'm open for suggestions, ideas, proposals and patches.
The w32 binary uses the w32 API for the IO access. This means
that it is possible to open disk devices, samba files, etc..
There is no disassembler, because this task is delegated to rasm
or rasm2 (objdump or any other disassembler) by using the '!'
system command.
The syntax of the commands is close to radare, but it is not the
same for simplicity reasons. The format is:
[1char-command][argumen...@][addr][:blocksize]
Here there are some example commands, enjoy :)
* dump 20 bytes at 0x1000
x...@0x1000
* print 48/struct-size structs of { lilendian short, lil dword,
lil int32 }
psdi@:48
* hexdump of a file
red -</bin/ls
* write bytes in hexa
w 9090 6b4a
* write string
w "hello world"
* truncate file to 128 bytes
r128
* remove 10 bytes at offset 0x300 (shrink file size)
r...@0x300
* slurp file
< dump.bin
* dump block of 1M from current seek
>dump.bin@:1M
* seek to offset 3GB
s3G
* search string
/"lib"
--pancake
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
------------------------------------------------------------------------
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
