/usr/share/doc/radare-doc/html/Section20.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 30 31 32 33 34 35 36 37 38 39 40 41 | <!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>Debugger environment</title>
<link rel="previous" href="Section20.3.7.html">
<link rel="ToC" href="contents.html">
<link rel="next" href="Section20.5.html">
</head>
<body>
<h1><a name="dbgenv"></a>20.4 Debugger environment</h1>
<p>
By default radare setups a clean environment for the child process to avoid antidebugging tricks like checking for '_' or 'LD_' and to avoid interferencing the stack address space compared to a real process execution.
</p>
<p>
The environment setup can be redefined using the 'file.dbg_env' eval variable pointing to a file with contents like:
</p>
<pre><code>[#comment][export ][variable]=["[value]"|@file]
</code></pre>
<p>
The format is similar to the shell 'export' command, but more flexible, because it supports loading variable contents from external files. Here's an example:
</p>
<pre><code># This is a sample file for file.dbg_env
PATH="/bin:/usr/bin"
HISTFILE=@/bin/ls
</code></pre>
<p>
The HISTFILE environment will be filled with the contents of the file '/bin/ls'.
</p>
<p>
Then run radare with these arguments:
</p>
<pre><code>$ radare -e file.dbg_env=env.txt -d ls
</code></pre>
<!-- version IDs:
$Id: radare.but 2009-04-25 pancake $
-->
</body>
</html>
|