Valgrind 3.5.0

Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect memory management and threading many bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory consumption of your programs. Valgrind distribution currently includes three tools: a detector error of memory, a cache (time) profiler and a heap (space) profiler. Valgrind is Open Source / Free Software and is freely available under the GNU General Public License. Here are some key features of "Valgrind" · Valgrind will save you hours of debugging time. With Valgrind tools you can automatically detect memory management and threading bugs many. It gives you confidence that your programs are free of many common bugs, some of which would take hours to manually find, or never occur at all. You can find and eliminate bugs before they become a problem. · Valgrind can help you accelerate your programs. With Valgrind tools you can make very detailed profiles to help speed up your programs. · Valgrind is free. free-as-in-speech: you can download, read the source code, make changes and send them, all within the GNU GPL. And free-as-in-beer: we do not pay for it. · Valgrind works on x86/Linux, AMD64/Linux and PPC32/Linux several platforms the most popular use. Valgrind works with all major Linux distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, Mandrake, etc. · Valgrind is easy to use. Valgrind uses dynamic binary translation, so you do not need to modify, recompile and link your applications. Just prefix your command line with valgrind and everything works. · Valgrind is not a toy. Valgrind is first and Foremost a tool for debugging and profiling system for large complex programs. We've had feedback from users working on projects with a maximum of 25 million lines of code. It has been used on projects of all sizes, from single-user personal projects, projects with hundreds of programmers. · Valgrind is suitable for any type of software. Valgrind has been used on almost any type of software imaginable: desktop applications, libraries, databases, games, web browsers, network servers, distributed control systems, managers of virtual reality, servers transaction, compilers, interpreters, virtual machines, telecommunication applications, embedded software, medical imaging, scientific programming, signal processing, video / audio programs, NASA Mars Lander vision and navigation systems Rover , software for business intelligence, financial software and banking, demons operating system, etc., etc. See a list of projects using Valgrind. · Valgrind is widely used. Valgrind has been used by thousands of programmers worldwide. We received comments from users in over 25 countries, including Belgium, the Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Italy, Netherlands, Norway, Poland, Portugal, Russia, Sweden , Switzerland, United Kingdom, Argentina, Brazil, Canada, USA, Australia, India, Japan, New Zealand, Singapore, South Africa and Israel. · Valgrind works with programs written in any language. Because Valgrind works directly with the binary program, it works with programs written in any programming language, they are compiled, just-in-time compiled or interpreted. Valgrind tools are largely intended for programs written in C and C + +, because programs written in these languages tend to have more bugs! But it may, for example, be used to debug and profile systems written in a mixture of languages. Valgrind has been used on programs written in part or entirely in C, C + +, Java, Perl, Python, assembler code, Fortran, Ada and many others. · Valgrind debugging and profiling your entire program. Unlike tools that require a recompilation step, gives you total Valgrind debugging and profiling of coverage of each instruction executed by your program, even within the library system. You can even use Valgrind on programs for which you do not have the source code. · Valgrind can be used with other tools. Valgrind can start GDB and attach it to your program to the point (s) where errors are detected, so that you can search and understand what was happening at the time. · Valgrind is available. Valgrind core consists of Valgrind, which provides a synthesis software CPU, and Valgrind tools, which plug into the heart, and the instrument and analyze the current program. Anyone can write powerful new tools that add arbitrary instrumentation programs. This is much easier than writing such tools from scratch. Valgrind This makes it ideal for experimenting with new types of debuggers, profilers, similar tools. · Valgrind is actively maintained. Valgrind developers who continuously work to fix bugs, improve Valgrind, and ensure that it works like new Linux distributions and libraries out. There are also mailing lists you can subscribe and contact us if you encounter problems. · So what's the catch? The main programs that are already much more slowly under Valgrind. Depending on the tool you use, the slowdown factor can range from 5 - 100. This slowdown is similar to that of similar debugging and profiling tools. But since you have to use Valgrind all the time, it is usually not too much trouble. The number of hours you save debugging will more than make up for it.