blob: 1c680a2753785d42f32b7811fbf033a386286858 (
plain)
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
42
43
44
|
====================
0: Table of contents
====================
0: Table of contents
1: Intro
2: Using the leak checker
========
1: Intro
========
Nautilus source tree is available from CVS (the latest-cutting edge
version) and in releases (tarballs).
If you plan to hack on Nautilus, please make sure you work from the
CVS version. The CVS version is available on GNOME CVS. The page
http://developer.gnome.org/tools/cvs.html details how to get started
with GNOME CVS.
If you want to contribute patches, please send mail to one of the nautilus
maintainers (listed in MAINTAINERS) and/or the nautilus mailing
list: <nautilus-list@lists.eazel.com> (subscriptions should be made to
<nautilus-list-request@lists.eazel.com> with "subscribe" as a
subject).
Patches should be made with 'cvs diff -pu >patch' and should conform to
Nautilus coding style as described in docs/style-guide.html Please
read other relevant documents in the docs directory too.
=========================
2: Using the leak checker
=========================
The leak checker is built as part of the eazel-tools gnome module.
Build that first before you continue.
Nautilus is set up to use the libleakcheck.so leak checking
library. To use it, run Nautilus with LD_PRELOAD set to the path to
the installed libleakcheck.so library. For example, if you are using a
Bourne-compatible shell, like bash, you can run Nautilus this way to
run with leak checking:
LD_PRELOAD=/gnome/lib/libleakcheck.so /gnome/bin/nautilus
|
