www.archive-org-2014.com » ORG » V » VALGRIND

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 74 . Archive date: 2014-06.

  • Title: Valgrind Home
    Descriptive info: .. Information.. About.. News.. Tool Suite.. Supported Platforms.. The Developers.. Source Code.. Current Releases.. Release Archive.. Variants / Patches.. Code Repository.. Valkyrie / GUIs.. Documentation.. Table of Contents.. Quick Start.. FAQ.. User Manual.. Download Manual.. Research Papers.. Books.. Contact.. Mailing Lists and IRC.. Bug Reports.. Feature Requests.. Contact Summary.. Commercial Support.. How to Help.. Contributing.. Project Suggestions.. Gallery.. Projects / Users.. Press / Media.. Awards.. Surveys.. Artwork / Clothing.. Current release:.. valgrind-3.. 9.. 0.. Valgrind is an instrumentation 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 six production-quality tools: a memory error detector, two thread error detectors, a cache and branch-prediction  ...   platforms: X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android (2.. 3.. x and later), X86/Android (4.. 0 and later), X86/Darwin and AMD64/Darwin (Mac OS X 10.. 7, with limited support for 10.. 8).. Valgrind is.. Open Source.. /.. Free Software.. , and is freely available under the.. GNU General Public License, version 2.. Recent News.. 31 October 2013: valgrind-3.. 0, for X86/Linux, AMD64/Linux, ARM/Linux, PPC32/Linux, PPC64/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android (2.. 8) is available.. (.. release notes.. ).. 21 October 2010: Valkyrie-2.. 0, a Qt4-based GUI for the Memcheck and Helgrind tools in Valgrind-3.. 6.. 0, is now available.. May 5 2010: Valgrind t-shirts are available for purchase at.. FreeWear.. org.. For each t-shirt sold, 3 &euro will be donated to the Valgrind project.. Copyright 2000-2013.. Valgrind Developers.. Best Viewed With A(ny) Browser..

    Original link path: /
    Open archive

  • Title: Valgrind: About
    Descriptive info: |.. About Valgrind.. Valgrind is a GPL'd system for debugging and profiling Linux programs.. With Valgrind's.. tool suite.. you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable.. You can also perform detailed profiling to help speed up your programs.. Why should you use Valgrind?.. Valgrind will save you hours of debugging time.. With Valgrind tools you can automatically detect many memory management and threading bugs.. This gives you confidence that your programs are free of many common bugs, some of which would take hours to find manually, or never be found at all.. You can find and eliminate bugs before they become a problem.. Valgrind can help you speed up your programs.. With Valgrind tools you can also perform very detailed profiling to help find bottlenecks in your programs.. Valgrind is free.. Free-as-in-speech: you can download it, read the source code, make modifications, and pass them on, all within the limits of the GNU GPL.. And free-as-in-beer: we aren't charging for it.. Valgrind runs on several popular platforms, such as x86/Linux, AMD64/Linux and PPC32/Linux.. Valgrind works with all the major Linux distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, Mandrake, etc.. Valgrind is easy to use.. Valgrind uses dynamic binary instrumentation, so you don't need to modify, recompile or relink your applications.. Just prefix your command line with valgrind and everything works.. Valgrind is not a toy.. Valgrind is first and foremost a debugging and profiling system for large, complex programs.. We have had feedback from users working on projects with up to 25 million lines of code.. It has been used on projects of all sizes, from single-user personal projects, to projects with hundreds of programmers.. Valgrind is suitable for any type of software.. Valgrind has been used with desktop applications, libraries, databases, games, web browsers, network servers, distributed control systems, virtual reality frameworks, transaction servers, compilers, interpreters, virtual machines, telecom applications, embedded software, medical imaging, scientific programs, signal processing programs, video/audio programs, business intelligence software, financial/banking software, operating system daemons, etc, etc.. See a list  ...   writing such tools from scratch.. This makes Valgrind ideal for experimenting with new kinds of program analysis tools.. It has been used for research purposes by people at the following universities: Cambridge, MIT, UC Berkeley, UC Santa Barbara, Carnegie Mellon, Cornell, University of New Mexico, Australian National University, University of Melbourne, TU Muenchen (Munich) and Graz University of Technology.. Valgrind is actively maintained.. The Valgrind developers are constantly working to fix bugs, improve Valgrind, and ensure it works as new Linux distributions and libraries come out.. There are also mailing lists you can subscribe to, and contact if you're having problems.. So what's the catch? The main one is that programs run significantly more slowly under Valgrind.. Depending on which 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 don't have to use Valgrind all the time, this usually isn't too much of a problem.. The hours you'll save debugging will more than make up for it.. When should you use Valgrind?.. It depends on your exact needs.. Here are some examples of when people use Valgrind's bug-detecting tools.. All the time.. For small programs with short run-times, when developing you can always run the program under a Valgrind tool (usually Memcheck), knowing that memory bugs will be found immediately.. In automatic testing.. By using Valgrind tools in your automatic unit, integration, system, or regression test, you can be confident no code will be unchecked.. After big changes.. To ensure new bugs haven't been introduced in the new code.. When a bug occurs.. Get instant feedback about what the bug is, where it occurred, and why.. When a bug is suspected.. Is your program behaving oddly? Use a Valgrind tool to discover if a bug is the cause.. Before a release.. To give you confidence that your new release is as stable and bug-free as possible.. As for Valgrind's profiling tools, use those whenever you want information about how your program is spending its time, or you want to speed it up..

    Original link path: /info/about.html
    Open archive

  • Title: Valgrind: News
    Descriptive info: Valgrind News.. Keep informed about news from Valgrind by subscribing to the.. valgrind-announce.. mailing list.. Below are a few of the important events in the history of Valgrind:.. July 1 2010: Initial support for Mac OS X 10.. 6 (Snow Leopard) has been folded into the trunk and is usable.. Support for 64-bit executables on 10.. 5 and 10.. 6 has also been improved.. Note that to build a 64-bit capable Valgrind, which is probably what you need on 10.. 6, you must use the configure-time flag "--build=amd64-darwin".. For more details see the.. repository.. page.. July 1 2010: Initial support for the SSE4.. 1/4.. 2 instruction set has been folded into the trunk, for 64-bit processes only at present.. The implementation is incomplete but is believed to cover all instructions generated by gcc-4.. 4/4.. 5 "-O3 -msse4.. 2".. Work on further coverage is ongoing.. May 6 2010: Initial support for ARM/Linux has been folded into the SVN trunk, and is usable on Ubuntu 9.. 04 and 9.. 10 for ARM.. Further development to support more recent Ubuntus and the full ARMv7 instruction set is in progress.. August 19 2009: valgrind-3.. 5.. 0, for X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux and X86/Darwin (Mac OS X) is available.. February 28 2009: valgrind-3.. 4.. 1, for X86/Linux, AMD64/Linux, PPC32/Linux, and PPC64/Linux is available.. January 2 2009: valgrind-3.. 0, for X86/Linux, AMD64/Linux, PPC32/Linux, and PPC64/Linux is available.. June 17 2008: We have a new.. books page.. June 4 2008: Valgrind 3.. 1, for x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux, is available.. December 7 2007: A new release, 3.. 0, is available for x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux (.. January 29 2007: A bug-fix release, 3.. 2.. 3, is available (.. 3.. 3 is almost identical to 3.. 2, but fixes a regression that unfortunately crept into 3.. January 22 2007: A bug-fix release, 3.. 2, is available (.. October 30 2006: The slides for  ...   soon.. September 22 2005: Please fill out our.. survey.. We will close the survey in about one week's time, depending on the response rate.. Update:.. We are extending the survey by one week because we are still getting a good number of responses each day.. Please fill out a survey if you have not already.. August 29 2005: A bug-fix release, 3.. 1 is available for x86-linux and amd64-linux (.. 1 fixes a significant number of bugs in 3.. 0, some of them critical.. If you use/distribute 3.. 0, an upgrade to 3.. 1 is recommended.. August 3 2005: A new stable version, 3.. 0 is a major new release, with support for both x86-linux and amd64-linux, and many other improvements.. August 1 2005: A new stable version, 2.. 1, is available.. March 24, 2005: A new stable release,.. valgrind 2.. , is available.. Relative to 2.. 0, 2.. 0 has improved thread and signal support, reduced memory consumption, and dozens of bug fixes.. March 12, 2005: The Valgrind website has been overhauled, and moved to.. www.. valgrind.. Many thanks to KDE for hosting the previous website.. March 12, 2005: A new mailing list,.. , has been created.. This low-volume list will receive announcements of new Valgrind releases.. August 31, 2004: A new stable release,.. 2.. 0 brings many improvements over 2.. 0, and includes the new Massif heap-profiling tool.. July 18 2004: A new developer release,.. 2 fixes many bugs in 2.. 1, and includes the new Massif heap-profiling tool.. March 12 2004: A new developer release,.. March 04 2004: An experimental PowerPC port is available.. February 15 2004: Valgrind CVS now includes.. Massif.. , a heap profiling tool.. January 27 2004: We have a new page listing.. January 15 2004: Valgrind awarded a merit (bronze).. Open Source Award.. read the interview.. December 14 2003: A new developer release,.. November 11 2003: A new stable release,..

    Original link path: /info/news.html
    Open archive

  • Title: Valgrind: Tool Suite
    Descriptive info: Valgrind's Tool Suite.. The Valgrind distribution includes the following debugging and profiling tools:.. Memcheck.. Cachegrind.. Callgrind.. Helgrind.. DRD.. Other Tools.. Memcheck detects memory-management problems, and is aimed primarily at C and C++ programs.. When a program is run under Memcheck's supervision, all reads and writes of memory are checked, and calls to malloc/new/free/delete are intercepted.. As a result, Memcheck can detect if your program:.. Accesses memory it shouldn't (areas not yet allocated, areas that have been freed, areas past the end of heap blocks, inaccessible areas of the stack).. Uses uninitialised values in dangerous ways.. Leaks memory.. Does bad frees of heap blocks (double frees, mismatched frees).. Passes overlapping source and destination memory blocks to memcpy() and related functions.. Memcheck reports these errors as soon as they occur, giving the source line number at which it occurred, and also a stack trace of the functions called to reach that line.. Memcheck tracks addressability at the byte-level, and initialisation of values at the bit-level.. As a result, it can detect the use of single uninitialised bits, and does not report spurious errors on bitfield operations.. Memcheck runs programs about 10--30x slower than normal.. Cachegrind is a cache profiler.. It performs detailed simulation of the I1, D1 and L2 caches in your CPU and so can accurately pinpoint the sources of cache misses in your code.. It identifies the number  ...   a program's heap.. It produces a graph showing heap usage over time, including information about which parts of the program are responsible for the most memory allocations.. The graph is supplemented by a text or HTML file that includes more information for determining where the most memory is being allocated.. Massif runs programs about 20x slower than normal.. Helgrind is a thread debugger which finds data races in multithreaded programs.. It looks for memory locations which are accessed by more than one (POSIX p-)thread, but for which no consistently used (pthread_mutex_) lock can be found.. Such locations are indicative of missing synchronisation between threads, and could cause hard-to-find timing-dependent problems.. It is useful for any program that uses pthreads.. It is a somewhat experimental tool, so your feedback is especially welcome here.. DRD is a tool for detecting errors in multithreaded C and C++ programs.. The tool works for any program that uses the POSIX threading primitives or that uses threading concepts built on top of the POSIX threading primitives.. While Helgrind can detect locking order violations, for most programs DRD needs less memory to perform its analysis.. Lackey, Nulgrind.. Lackey and Nulgrind are also included in the Valgrind distribution.. They don't do very much, and are there for testing and demonstrative purposes.. Several other Valgrind tools have been created: you can find a list of them on the..

    Original link path: /info/tools.html
    Open archive

  • Title: Valgrind: Supported Platforms
    Descriptive info: Current.. The Valgrind 3.. 7.. X series supports the following platforms.. x86/Linux:.. support is mature and almost complete.. AMD64/Linux:.. Note that AMD64 is just another name for x86-64, and that Valgrind works fine on Intel machines.. PPC32/Linux:.. support is new but fairly complete.. PPC64/Linux:.. x86/Darwin (Mac OS X):.. support is new.. AMD64/Darwin (Mac OS X):.. S390X/Linux:.. support is new in 3.. ARM/Linux.. support for ARMv7 is fairly complete.. ARM/Android.. MIPS32/Linux.. 8.. On Linux, you must be running kernel 2.. X or later, and glibc 2.. X or later.. That covers the vast majority of installed systems at present.. On Mac OS X you must be running 10.. x or later.. For details of which distributions the current release (valgrind-3.. 0) builds and runs its regression tests on, see the.. x86/FreeBSD:.. The FreeBSD port has been developed since Valgrind 2.. X.. The FreeBSD porting team actively maintains the port, typically tracking Valgrind releases within a week or two.. Snapshots are on this.. FreeBSD page.. Experimental.. The following experimental ports have been done.. Note that they have varying levels of completeness and may not work reliably, and may target older versions of Valgrind.. Doug Rabson and others haved done a fairly complete port of Valgrind 3.. Snapshots of the work in progress are at.. this FreeBSD page.. x86/NetBSD:.. Eric Auge, Kailash Sethuraman and Peter Bex are doing a port of Valgrind 3.. X, available at.. this  ...   not simply a technical exercise: you also need to make a convincing case that the effort will be worth it, and that the port will be supported properly, at least in the foreseeable future.. The following table summarises our current porting priorities.. Linux.. Darwin.. *BSD.. Solaris.. x86.. done.. low.. amd64.. ppc32.. ppc64.. s390x.. arm.. medium.. mips.. in progress.. Some experimental ports have been worked on, as mentioned above.. A less mature port for x86/Solaris has also been worked on.. Of the other table entries Arm/Linux is the most interesting.. MIPS/Linux, x86/BSD, amd64/BSD and x86/Solaris are lower priorities.. There are many platforms not mentioned here.. Some are of little interest (eg.. SPARC/*, */AIX).. Some would be technically difficult (eg.. IA64/*).. In particular Windows is not under consideration here because porting to it would require so many changes it would almost be a separate project.. (However, Valgrind + Wine can be made to work with some effort.. ) Also, non-open-source OSes are difficult to deal with; being able to see the OS and associated (libc) source code makes things much easier.. However, Valgrind is quite usable in conjunction with Wine, which means that it is possible to run Windows programs under Valgrind with some effort.. This message states our porting rationale and current priorities.. As ever we retain a flexible approach, and are interested in hearing your comments/porting needs if you have any.. November 24, 2011..

    Original link path: /info/platforms.html
    Open archive

  • Title: Valgrind: The Developers
    Descriptive info: The Valgrind Developers.. The Valgrind developers are a loose-knit group of people from all over the world who contribute to Valgrind and have direct write access to the Valgrind repository.. Please feel free to send praise, abuse, ideas, etc, to them.. If you want to become a valgrind developer, then the first thing you should do is join the.. valgrind-developers.. mailing list and start contributing to the development of Valgrind.. Valgrind Developers / Contributors.. Cerion Armour-Brown.. Cerion worked on PowerPC instruction set support using the Vex dynamic-translation framework.. Christian Borntraeger.. Christian worked on and helps maintain the s390/Linux port.. Jeremy Fitzhardinge.. Jeremy wrote the original Helgrind and totally overhauled low-level syscall/signal and address space layout stuff, among many other improvements.. Tom Hughes.. Tom did a vast number of bug fixes, and helped out with support for more recent Linux/glibc versions.. Petar Jovanovic and Dejan Jevtic.. Petar and Dejan wrote and maintain the mips32-linux port.. Florian Krohm.. Florian developed and maintains the s390/Linux port.. He also improved the regression test system and does bugfixing and static analysis of the code base.. Carl Love and Maynard Johnson.. Carl and Maynard contributed IBM  ...   mismatch checking stuff and various other bits and pieces, and acted as our KDE liaison.. Nicholas Nethercote.. Nick did the core/tool generalisation, wrote Cachegrind and Massif, and tons of other stuff.. Julian Seward.. Julian was the original designer and author of Valgrind, created the dynamic translation frameworks, wrote Memcheck, Helgrind and SGCheck, and did lots of other things.. Bart Van Assche.. Bart is the author of Drd, a tool for finding bugs in threaded programs, that first shipped in the 3.. 0 release.. Robert Walsh.. Robert added file descriptor leakage checking, new library interception machinery, support for client allocation pools, and minor other tweakage.. Philippe Waroquiers.. Philippe wrote and maintains the embedded GDB server.. He also made a bunch of performance, memory-use and correctness fixes across diverse parts of the system.. Josef Weidendorfer.. Josef wrote and maintains Callgrind.. Frederic Gobry helped with autoconf and automake.. Daniel Berlin modified readelf's dwarf2 source line reader, written by Nick Clifton, for use in Valgrind.. Michael Matz and Simon Hausmann modified the GNU binutils demangler(s) for use in Valgrind.. And lots and lots of other people sent bug reports, patches, and very helpful feedback..

    Original link path: /info/developers.html
    Open archive

  • Title: Valgrind: Current Releases
    Descriptive info: The complete source code, including documentation, is available as a tarball for the current release.. For downloadable / browseable manual packages, go to the.. For older releases, see the.. If you would like to be notified when a new valgrind release is made, you can subscribe to the Valgrind.. announcements.. valgrind 3.. 0 (tar.. bz2).. [10MB] - 31 October 2013.. For {x86,amd64,arm,ppc32,ppc64,s390x,mips32,mips64}-linux, arm-android (2.. 3 and later), x86-android (4.. 0 and later) and {x86,amd64}-darwin (Mac OS X 10.. md5: 0947de8112f946b9ce64764af7be6df2.. You may want to look at the.. 0 release notes.. 0 is feature release with many improvements and the usual collection of bug fixes.. This release adds support for MIPS64/Linux and improves support for Mac OS X 10.. 8 (Mountain Lion).. Intel AVX2 and Power POWER8 instructions are supported.. Initial support for hardware transactional memory on Intel and POWER platforms has been added.. Accuracy of Memcheck on vectorized code has been improved.. There are many smaller refinements and new features.. See the.. for details.. This release  ...   has an XML merging tool for Memcheck outputs (vk_logmerge).. This tarball is known to build and work with valgrind-3.. 0 and valgrind-3.. This version of Valkyrie does not support any version of Valgrind prior to 3.. If you want to use Valkyrie with an older Valgrind version, we recommend you instead upgrade your Valgrind to 3.. 0 and use this version of Valkyrie.. RPMs / Binaries.. We do not distribute binaries or RPMs.. The releases available on this website contain the source code and have to be compiled in order to be installed on your system.. Many Linux distributions come with valgrind these days, so if you do not want to compile your own, go to your distribution's download site.. System Requirements.. Programs running under Valgrind run significantly more slowly, and use much more memory -- e.. g.. more than twice as much as normal under the Memcheck tool.. Therefore, it's best to use Valgrind on the most capable machine you can get your hands on..

    Original link path: /downloads/current.html
    Open archive

  • Title: Valgrind: Release Archive
    Descriptive info: Here you will find the code for past Valgrind releases.. Release notes for these releases are.. here.. The current release is on the.. Please note that the releases on this page are listed for archaeological / historical purposes only, and are no longer supported.. 1 (tar.. bz2) [5184Kb] md5: b5f039dd2271aaf9ae570ab4116f87c7.. bz2) [5175Kb] md5: 1b0fe1219e1a583ff8c2db54ed2265e6..  ...   md5: 978847992b136c8d8cb5c6559a91df1c.. 2 (tar.. bz2) [4016Kb] md5: de3f68da0c8b7fc72b8fded95a9aebbc.. [4052Kb] md5: 9407d33961186814cef0e6ecedfd6318.. [4059Kb] md5: c418026ce7c38a740ef17efe59509fcf.. [3074Kb] md5: 3bbfafedb59c19bf75977381ce2eb6d7.. [3054Kb] md5: d92156e9172dc6097e56c69ea9c88013.. [2688Kb] md5: c29efdb7d1a93440f5644a6769054681.. [2679Kb] md5: e976a343c61d9505162f595a8aeb09c1.. [1078Kb] md5: 8ada0f37ddd940032b85ea859fedb037.. [965Kb] md5: 30dc51f6fc94751b90b04af9c2e2c656.. bz2) [962Kb] md5: 585e3ac5f7b86d6cd3e2bed07af732de.. [923 Kb] md5: 0010c3e8f054ecc633151c62044b646d.. [762 Kb] md5: 3e4056dd45163a5f555a23ced2f95191.. [710Kb] md5: 1f6a90d0ca494fb75eaeef498e8252b5.. valgrind 1.. 6 (tar.. [660Kb] md5: 8d2ef95c9438d399d45698ce2d0a0562..

    Original link path: /downloads/old.html
    Open archive

  • Title: Valgrind: Variants / Patches
    Descriptive info: Variants and Patches.. Several other Valgrind tools have been created.. Some of these can plug directly into an existing Valgrind installation, but some require downloading a whole Valgrind distribution which contains a specially modified core.. Please note that some of these are experimental, and may not work 100%.. Nick Nethercote.. has built.. several experimental tools.. : a Bounds Checker, a Signal-Handler Checker, and a Data Flow Tracer.. He also has an experimental Valgrind distribution that has an interactive command line.. has.. several patches.. , mostly to do with threading.. His patches are regularly merged with the CVS head; this set represents the currently unmerged patches.. some useful patches.. : one adds watchpoints on memory locations, the other adds support for pool-based allocators (which has been merged into Valgrind proper).. Adam Gundy.. arg at cyberscience com supplied a variant of the 20031012 stable release that is capable of running Wine on Valgrind.. A big thanks  ...   want to valgrindify Wine and apps running on it.. For "normal" Linux applications, use the standard valgrind version.. Valgrind 20031012-wine should be used with a recent CVS version of Wine.. Provided you have the PDB files for executables and DLLs, valgrind will give stack traces for MSVC compiled code.. Multi-threaded programs are fully supported.. Leak checking does not work at the moment.. Vince Weaver.. has written.. three tools.. : a cache tool trace generator, a SimPoint data generator (which has been merged into the Valgrind distribution as the BBV tool as part of release 3.. 0), and a TAXI-compatible stream generator (TAXI decodes pre-decoded x86 instruction streams into PISA uops and runs through a modified version of the PISA SimpleScalar).. Michael Meeks.. Iogrind.. , a prototype I/O profiling tool.. Konstantin Serebryany.. and.. Timur Iskhodzhanov.. have written.. ThreadSanitizer.. , a data race detector.. It has some similarities to Helgrind and DRD but also some differences..

    Original link path: /downloads/variants.html
    Open archive

  • Title: Valgrind: Code Repository
    Descriptive info: Source Code Repository.. If you are looking for a stable release of the source code, you should download it from the.. The rest of this page describes how to get hold of code at the leading edge of the development effort.. Such code may not work properly.. The actively developed, current (v3.. 0 and later) code is in a.. Subversion.. (SVN) repository at valgrind.. If you are doing any development work, please do it using the code from the current repository at valgrind.. org!.. The Current (3.. 0 and later) Repository..  ...   build the checked out code, follow the instructions in the.. README.. file that the checkout should give you.. Alternatively, the following should work:.. cd valgrind.. /autogen.. sh.. /configure --prefix=.. make make install.. To do the checkout, you'll need a Subversion client, version 1.. 0 or later.. Versions prior to 1.. 0 do not properly handle the symbolic links in our tree.. To do the build, you'll need automake version 1.. 10 or later and a compatible version of autoconf (e.. 68).. These should come as standard on any non-ancient Linux distribution..

    Original link path: /downloads/repository.html
    Open archive

  • Title: Valgrind: Valkyrie / GUIs
    Descriptive info: Graphical User Interfaces.. One of the most requested features for Valgrind is a graphical user interface to help with use and configuration.. is a Qt4-based GUI for the Memcheck and Helgrind tools in the Valgrind 3.. X line, developed and maintained by the Valgrind Developers.. Valkyrie also includes an auxiliary tool which merges XML output from multiple Memcheck runs into a single XML file, and optionally displays the merged result in the GUI.. You can see some.. screenshots here.. The complete source code for the current release, including documentation, is available as a tarball from the.. Valgrind download page.. The code under active development is in a Subversion repository (and may not work properly).. To check out  ...   set and other GNOME libraries for the X-Windows environment.. KDevelop.. lets you use Valgrind as a plugin.. Tool Gear's.. MemcheckView.. package provides scripts for running Valgrind's Memcheck tool on serial and parallel (MPI) programs and a Qt-based GUI for interpreting Memcheck's results (requires XML output from Memcheck).. The MemcheckView GUI groups the Memcheck messages by error type and allows the viewing of the relevant source code for all levels of each message's call stack.. The MemcheckView package and how to use it is described in much more detail here:.. https://computing.. llnl.. gov/code/memcheck/.. Eclipse has a GUI plugin to integrate Valgrind into its C++ Development Tools.. Information on use and downloads links can be found here:.. http://www.. eclipse.. org/linuxtools/projectPages/valgrind/..

    Original link path: /downloads/guis.html
    Open archive





  • Archived pages: 74