512c5cad6c37edb98ae91c8a76c3a291

Edit file

File name : dist.readme.html

Content :

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>4. README</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.news.old.html" title="3. OLDER NEWS">
<link rel="next" href="dist.readme-missing.html" title="5. README_MISSING_SYSCALL_OR_IOCTL">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div><table class="nav" width="100%" cellspacing="3" cellpadding="3" border="0" summary="Navigation header"><tr>
<td width="22px" align="center" valign="middle"><a accesskey="p" href="dist.news.old.html"><img src="images/prev.png" width="18" height="21" border="0" alt="Prev"></a></td>
<td width="25px" align="center" valign="middle"><a accesskey="u" href="dist.html"><img src="images/up.png" width="21" height="18" border="0" alt="Up"></a></td>
<td width="31px" align="center" valign="middle"><a accesskey="h" href="index.html"><img src="images/home.png" width="27" height="20" border="0" alt="Up"></a></td>
<th align="center" valign="middle">Valgrind Distribution Documents</th>
<td width="22px" align="center" valign="middle"><a accesskey="n" href="dist.readme-missing.html"><img src="images/next.png" width="18" height="21" border="0" alt="Next"></a></td>
</tr></table></div>
<div class="chapter">
<div class="titlepage"><div><div><h1 class="title">
<a name="dist.readme"></a>4. README</h1></div></div></div>
<div class="literallayout"> 
      Release notes for Valgrind 
~~~~~~~~~~~~~~~~~~~~~~~~~~ 
If you are building a binary package of Valgrind for distribution, 
please read README_PACKAGERS.  It contains some important information. 
 
If you are developing Valgrind, please read README_DEVELOPERS.  It contains 
some useful information. 
 
For instructions on how to build/install, see the end of this file. 
 
If you have problems, consult the FAQ to see if there are workarounds. 
 
 
Executive Summary 
~~~~~~~~~~~~~~~~~ 
Valgrind is a framework for building dynamic analysis tools. There are 
Valgrind tools that can automatically detect many memory management 
and threading bugs, and profile your programs in detail. You can also 
use Valgrind to build new tools. 
 
The Valgrind distribution currently includes seven production-quality 
tools: a memory error detector, two thread error detectors, a cache 
and branch-prediction profiler, a call-graph generating cache and 
branch-prediction profiler, and two heap profilers. It also includes 
one experimental tool: a SimPoint basic block vector generator. 
 
Valgrind is closely tied to details of the CPU, operating system and to 
a lesser extent, compiler and basic C libraries. This makes it difficult 
to make it portable.  Nonetheless, it is available for the following 
platforms:  
 
- X86/Linux 
- AMD64/Linux 
- PPC32/Linux 
- PPC64/Linux 
- ARM/Linux 
- ARM64/Linux 
- x86/macOS 
- AMD64/macOS 
- S390X/Linux 
- MIPS32/Linux 
- MIPS64/Linux 
- nanoMIPS/Linux 
- X86/Solaris 
- AMD64/Solaris 
- X86/FreeBSD 
- AMD64/FreeBSD 
 
Note that AMD64 is just another name for x86_64, and Valgrind runs fine 
on Intel processors.  Also note that the core of macOS is called 
"Darwin" and this name is used sometimes. 
 
Valgrind is licensed under the GNU General Public License, version 2.  
Read the file COPYING in the source distribution for details. 
 
However: if you contribute code, you need to make it available as GPL 
version 2 or later, and not 2-only. 
 
 
Documentation 
~~~~~~~~~~~~~ 
A comprehensive user guide is supplied.  Point your browser at 
$PREFIX/share/doc/valgrind/manual.html, where $PREFIX is whatever you 
specified with --prefix= when building. 
 
 
Building and installing it 
~~~~~~~~~~~~~~~~~~~~~~~~~~ 
To install from the GIT repository: 
 
  0. Clone the code from GIT: 
     git clone https://sourceware.org/git/valgrind.git 
     There are further instructions at 
     http://www.valgrind.org/downloads/repository.html. 
 
  1. cd into the source directory. 
 
  2. Run ./autogen.sh to setup the environment (you need the standard 
     autoconf tools to do so). 
 
  3. Continue with the following instructions... 
 
To install from a tar.bz2 distribution: 
 
  4. Run ./configure, with some options if you wish.  The only interesting 
     one is the usual --prefix=/where/you/want/it/installed. 
 
  5. Run "make". 
 
  6. Run "make install", possibly as root if the destination permissions 
     require that. 
 
  7. See if it works.  Try "valgrind ls -l".  Either this works, or it 
     bombs out with some complaint.  In that case, please let us know 
     (see http://valgrind.org/support/bug_reports.html). 
 
Important!  Do not move the valgrind installation into a place 
different from that specified by --prefix at build time.  This will 
cause things to break in subtle ways, mostly when Valgrind handles 
fork/exec calls. 
 
 
The Valgrind Developers 
 
    </div>
</div>
<div>
 <table class="nav" width="100%" cellspacing="3" cellpadding="2" border="0" summary="Navigation footer">
<tr>
<td rowspan="2" width="40%" align="left">
<a accesskey="p" href="dist.news.old.html">&lt;&lt; 3. OLDER NEWS</a> </td>
<td width="20%" align="center"><a accesskey="u" href="dist.html">Up</a></td>
<td rowspan="2" width="40%" align="right"> <a accesskey="n" href="dist.readme-missing.html">5. README_MISSING_SYSCALL_OR_IOCTL &gt;&gt;</a>
</td>
</tr>
<tr><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td></tr>
</table>
</div>
</body>
</html>

Gel4y Mini Shell

Edit file