/usr/share/doc/radare-doc/html/Section16.3.4.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 | <!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>Virtual machine MMU</title>
<link rel="previous" href="Section16.3.3.html">
<link rel="ToC" href="contents.html">
<link rel="next" href="Section16.4.html">
</head>
<body>
<h1><a name="codeanal-mmu"></a>16.3.4 Virtual machine MMU</h1>
<p>
The MMU of the virtual machine is linked with the internal radare IO. This means that you can use for example map multiple files in a virtual space with 'o file <virtual-address>' to create a static environment of a debugger one.
</p>
<p>
If you are using the radare virtual machine to evaluate code and determine register values and so on you will not be interested into real memory writes because this will make the memory of the debugged program be modified without executing real code and then probably segfault.
</p>
<p>
To solve this problem. The radare virtual machine implements a cache system that records all the write operations and map them into the read operations. This option can be enabled and disabled with tme 'vm.realio' eval variable:
</p>
<pre><code>[0x4A13B8C0]> e vm.realio = true ; disable cache write protection
</code></pre>
<!-- version IDs:
$Id: radare.but 2009-04-25 pancake $
-->
</body>
</html>
|