This file is indexed.

/usr/share/doc/radare-doc/html/Section2.2.html is in radare-doc 1:1.5.2-4.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=US-ASCII">
<title>Common configuration variables</title>
<link rel="previous" href="Section2.1.html">
<link rel="ToC" href="contents.html">
<link rel="next" href="Chapter3.html">
</head>
<body>
<h1><a name="common-conf"></a>2.2 Common configuration variables</h1>
<p>
Here's a list of the most common eval configuration variables, you can get the complete list using the 'e' command without arguments or just use 'e cfg.' (ending with dot, to list all the configuration variables of the cfg. space).
</p>
<pre><code>asm.arch
</code></pre>
<p>
Defines the architecture to be used while disassembling (pd, pD commands) and analyzing code ('a' command). Currently it handles 'intel32', 'intel64', 'mips', 'arm16', 'arm' 'java', 'csr', 'sparc', 'ppc', 'msil' and 'm68k'.
</p>
<p>
It is quite simple to add new architectures for disassembling and analyzing code, so there is an interface adapted for the GNU disassembler and others for udis86 or handmade ones.
</p>
<p>
Setting asm.arch to 'objdump' the disassembly engine will use asm.objdump to disasemble the current block. For the code analysis the core will use the previous architecture defined in asm.arch.
</p>
<pre><code>[0x4A13B8C0]&gt; e asm.objdump 
objdump -m i386 --target=binary -D
[0x4A13B8C0]&gt; e asm.arch 
intel
[0x4A13B8C0]&gt; pd 2
      |    0x4A13B8C0,       eip: 89e0            mov eax, esp        
      |    0x4A13B8C2             e839070000      call 0x4a13c000       ; 1 = 0x4a13c000
[0x4A13B8C0]&gt; e asm.arch =objdump
[0x4A13B8C0]&gt; pd
      |    0x4A13B8C0, eip
   0:   89 e0                   mov    eax,esp
   2:   e8 39 07 00 00          call   0x740
   7:   89 c7                   mov    edi,eax
   9:   e8 e2 ff ff ff          call   0xfffffff0
   ...
</code></pre>
<p>
This is useful for disassembling files in architectures not supported by radare. You should understand 'objdump' as 'your-own-disassembler'.
</p>
<pre><code>asm.bits
</code></pre>
<p>
This variable will change the 'asm.arch' one (in radare1) and viceversa (is determined by asm.arch). It determines the size in bits of the registers for the selected architecture. This is 8, 16, 32, 64.
</p>
<pre><code>asm.syntax
</code></pre>
<p>
Defines the syntax flavour to be used while disassembling. This is currently only targeting the udis86 disassembler for the x86 (32/64 bits). The supported values are 'intel' or 'att'.
</p>
<pre><code>asm.pseudo
</code></pre>
<p>
Boolean value that determines which string disassembly engine to use (the native one defined by the architecture) or the one filtered to show pseudocode strings. This is 'eax=ebx' instead of a 'mov eax, ebx' for example.
</p>
<pre><code>asm.section
</code></pre>
<p>
Shows or hides section name (based on flags) at the left of the address.
</p>
<pre><code>asm.os
</code></pre>
<p>
Defines the target operating system of the binary to analyze. This is automatically defined by 'rabin -rI' and it's useful for switching between the different syscall tables and perform different depending on the OS.
</p>
<pre><code>asm.flags
</code></pre>
<p>
If defined to 'true' shows the flags column inside the disassembly.
</p>
<pre><code>asm.lines
</code></pre>
<p>
Draw lines at the left of the offset in the dissassemble print format (pd, pD) to graphically represent jumps and calls inside the current block.
</p>
<pre><code>asm.linesout
</code></pre>
<p>
When defined as 'true', also draws the jump lines in the current block that goes ouside of this block.
</p>
<pre><code>asm.linestyle
</code></pre>
<p>
Can get 'true' or 'false' values and makes the line analysis be performed from top to bottom if false or bottom to top if true. 'false' is the optimal and default value for readability.
</p>
<pre><code>asm.offset
</code></pre>
<p>
Boolean value that shows or hides the offset address of the disassembled opcode.
</p>
<pre><code>asm.profile
</code></pre>
<p>
Set how much information is showed to the user on disassembly. Can get the values 'default', 'simple', 'debug' and 'full'.
</p>
<p>
This eval will modify other asm. variables to change the visualization properties for the disassembler engine. 'simple' asm.profile will show only offset+opcode, and 'debug' will show information about traced opcodes, stack pointer delta, etc..
</p>
<pre><code>asm.trace
</code></pre>
<p>
Show tracing information at the left of each opcode (sequence number and counter). This is useful to read execution traces of programs.
</p>
<pre><code>asm.bytes
</code></pre>
<p>
Boolean value that shows or hides the bytes of the disassebled opcode.
</p>
<pre><code>dbg.focus
</code></pre>
<p>
Can get a boolean value. If true, radare will ignore events from non selected PIDs.
</p>
<pre><code>cfg.bigendian
</code></pre>
<p>
Choose the endian flavour 'true' for big, 'false' for little.
</p>
<pre><code>file.id
</code></pre>
<p>
When enabled (set it up to '1' or 'true'). Runs rabin -rI after opening the target file and tries to identify the file type and setup the virtual, physical address (io.vaddr, io.paddr) and stuff like that.
</p>
<pre><code>file.analyze
</code></pre>
<p>
Runs '<code>.af* @@ sym.</code>' and '<code>.af* @ entrypoint</code>', after resolving the symbols while loading the binary, to determine the maximum information about the code analysis of the program. This will not be used while opening a project file, so it is preloaded. This option requires file.id and file.flag to be true.
</p>
<pre><code>file.flag
</code></pre>
<p>
Finds all the information of the target binary and setup flags to point symbols (imports, exports), sections, maps, strings, etc.
</p>
<p>
This command is commonly used with file.id.
</p>
<pre><code>scr.color
</code></pre>
<p>
This boolean variable allows to enable or disable the colorized output
</p>
<pre><code>scr.seek
</code></pre>
<p>
This variable accepts an expression, a pointer (eg. eip), etc. radare will automatically seek to make sure its value is always within the limits of the screen.
</p>
<pre><code>cfg.fortunes
</code></pre>
<p>
Enables or disables the 'fortune' message at the begging of the program
</p>

<!-- version IDs:
$Id: radare.but 2009-04-25 pancake $
-->
</body>
</html>