The Official Radare2 Book - страница 11
Usually, serial consoles may work with 0 or 1, while xterms may support up to 3. RCons will try to find the closest color scheme for your theme when you choose a different them with the eco command.
It is possible to configure the color of almost any element of disassembly output. For *NIX terminals, r2 accepts color specification in RGB format. To change the console color palette use ec command.
Type ec to get a list of all currently used colors. Type ecs to show a color palette to pick colors from:
You can create your own color theme, but radare2 have its own predefined ones. Use the eco command to list or select them.
After selecting one, you can compare between the color scheme of the shell and the current theme by pressing Ctrl-Shift and then right arrow key for the toggle.
In visual mode use the R key to randomize colors or choose the next theme in the list.
Below is a list of the most frequently used configuration variables. You can get a complete list by issuing e command without arguments. For example, to see all variables defined in the "cfg" namespace, issue e cfg. (mind the ending dot). You can get help on any eval configuration variable by using e? cfg.
The e?? command to get help on all the evaluable configuration variables of radare2. As long as the output of this command is pretty large you can combine it with the internal grep ~ to filter for what you are looking for:
The Visual mode has an eval browser that is accessible through the Vbe command.
Defines the target CPU architecture used for disassembling (pd, pD commands) and code analysis (a command). You can find the list of possible values by looking at the result of e asm.arch=? or rasm2 -L. It is quite simple to add new architectures for disassembling and analyzing code. There is an interface for that. For x86, it is used to attach a number of third-party disassembler engines, including GNU binutils, Udis86 and a few handmade ones.
Determines width in bits of registers for the current architecture. Supported values: 8, 16, 32, 64. Note that not all target architectures support all combinations for asm.bits.
Changes syntax flavor for disassembler between Intel and AT&T. At the moment, this setting affects Udis86 disassembler for Intel 32/Intel 64 targets only. Supported values are intel and att.
A boolean value to set the psuedo syntax in the disassembly. "False" indicates a native one, defined by the current architecture, "true" activates a pseudocode strings format. For example, it'll transform :
│ 0x080483ff e832000000 call 0x8048436
│ 0x08048404 31c0 xor eax, eax
│ 0x08048406 0205849a0408 add al, byte [0x8049a84]
│ 0x0804840c 83f800 cmp eax, 0
│ 0x0804840f 7405 je 0x8048416
to
│ 0x080483ff e832000000 0x8048436 ()
│ 0x08048404 31c0 eax = 0
│ 0x08048406 0205849a0408 al += byte [0x8049a84]
│ 0x0804840c 83f800 var = eax - 0
│ 0x0804840f 7405 if (!var) goto 0x8048416
It can be useful while disassembling obscure architectures.
Selects a target operating system of currently loaded binary. Usually, OS is automatically detected by rabin -rI. Yet, asm.os can be used to switch to a different syscall table employed by another OS.
If defined to "true", disassembler view will have flags column.
If set to "true", draw lines at the left of the disassemble output (pd, pD commands) to graphically represent control flow changes (jumps and calls) that are targeted inside current block. Also, see asm.lines.out.
When defined as "true", the disassembly view will also draw control flow lines that go outside of the block.
A boolean value which changes the direction of control flow analysis. If set to "false", it is done from top to bottom of a block; otherwise, it goes from bottom to top. The "false" setting seems to be a better choice for improved readability and is the default one.