← Back to branch summary

~bkerensa/ubuntu/raring/valgrind/merge-from-deb

« back to all changes in this revision

Viewing changes to docs/html/dist.readme-developers.html

  • Committer: Bazaar Package Importer
  • Author(s): Andrés Roldán
  • Date: 2008-06-13 02:31:40 UTC
  • mto: (1.4.1 upstream) (2.2.1 squeeze)
  • mto: This revision was merged to the branch mainline in revision 24.
  • Revision ID: james.westby@ubuntu.com-20080613023140-iwk33rz9rhvfkr96
Import upstream version 3.3.1

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/html/dist.readme-developers.html
1
 
<html xmlns:cf="http://docbook.sourceforge.net/xmlns/chunkfast/1.0">
 
1
<html>
2
2
<head>
3
3
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
4
<title>7.�README_DEVELOPERS</title>
5
5
<link rel="stylesheet" href="vg_basic.css" type="text/css">
6
 
<meta name="generator" content="DocBook XSL Stylesheets V1.69.0">
 
6
<meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
7
7
<link rel="start" href="index.html" title="Valgrind Documentation">
8
8
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
9
9
<link rel="prev" href="dist.readme-missing.html" title="6.�README_MISSING_SYSCALL_OR_IOCTL">
33
33
This�allows�you�to�compile�and�run�with�"make"�instead�of�"make�install",<br>
34
34
saving�you�time.<br>
35
35
<br>
 
36
Or,�you�can�use�the�'vg-in-place'�script�which�does�that�for�you.<br>
 
37
<br>
36
38
I�recommend�compiling�with�"make�--quiet"�to�further�reduce�the�amount�of<br>
37
39
output�spewed�out�during�compilation,�letting�you�actually�see�any�errors,<br>
38
40
warnings,�etc.<br>
88
90
a�particular�tool)�requires�a�bit�more�trickery�but�can�be�achieved<br>
89
91
without�too�much�problem�by�following�these�steps:<br>
90
92
<br>
91
 
(1)�Set�VALGRIND_LAUNCHER�to�&lt;prefix&gt;/bin/valgrind:<br>
92
 
<br>
93
 
����export�VALGRIND_LAUNCHER=/usr/local/bin/valgrind<br>
94
 
<br>
95
 
(2)�Run�"gdb�&lt;prefix&gt;/lib/valgrind/&lt;platform&gt;/&lt;tool&gt;":<br>
96
 
<br>
97
 
����gdb�/usr/local/lib/valgrind/ppc32-linux/lackey<br>
 
93
(1)�Set�VALGRIND_LAUNCHER�to�point�to�the�valgrind�executable.��Eg:<br>
 
94
<br>
 
95
������export�VALGRIND_LAUNCHER=/usr/local/bin/valgrind<br>
 
96
<br>
 
97
����or�for�an�uninstalled�version�in�a�source�directory�$DIR:<br>
 
98
<br>
 
99
������export�VALGRIND_LAUNCHER=$DIR/coregrind/valgrind<br>
 
100
<br>
 
101
(2)�Run�gdb�on�the�tool�executable.��Eg:<br>
 
102
<br>
 
103
������gdb�/usr/local/lib/valgrind/ppc32-linux/lackey<br>
 
104
<br>
 
105
����or<br>
 
106
<br>
 
107
������gdb�$DIR/.in_place/x86-linux/memcheck<br>
98
108
<br>
99
109
(3)�Do�"handle�SIGSEGV�SIGILL�nostop�noprint"�in�GDB�to�prevent�GDB�from<br>
100
110
����stopping�on�a�SIGSEGV�or�SIGILL:<br>
111
121
<br>
112
122
����(gdb)�run�pwd<br>
113
123
<br>
 
124
Steps�(1)--(3)�can�be�put�in�a�.gdbinit�file,�but�any�directory�names�must<br>
 
125
be�fully�expanded�(ie.�not�an�environment�variable).<br>
114
126
<br>
115
127
Self-hosting<br>
116
128
~~~~~~~~~~~~<br>