diff options
| author | Sam Thursfield <sam@afuera.me.uk> | 2019-09-10 17:13:30 +0200 |
|---|---|---|
| committer | Sam Thursfield <sam@afuera.me.uk> | 2019-09-14 12:56:38 +0200 |
| commit | b68cef0297254aac79c856c5891aab110b03a4ff (patch) | |
| tree | 850fe307f72c1ad08f2bb002ad1eca2e5b58ddbf /HACKING.md | |
| parent | e072f03b8bb5a88d5b094318a369345a774a5db0 (diff) | |
| download | tracker-b68cef0297254aac79c856c5891aab110b03a4ff.tar.gz | |
Rework the tracker-sandbox utility (again)
This fixes https://gitlab.gnome.org/GNOME/tracker/issues/111 and also
simplifies the instructions in the README for running Tracker from
the build tree.
The sandbox utility is now executed from the top directory by running:
python3 -m utils.trackertestutils
Previously, due to importing stuff from trackertestutils. you needed to
run it from the utils/ directory or set PYTHONPATH appropriately.
Additionally, tracker-miners.git will ship a 'run-uninstalled' script
to provide convenient access to the sandbox script and allow running
Tracker from the build tree.
Diffstat (limited to 'HACKING.md')
| -rw-r--r-- | HACKING.md | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/HACKING.md b/HACKING.md index b907f3112..dea503369 100644 --- a/HACKING.md +++ b/HACKING.md @@ -33,8 +33,8 @@ CI. # Attaching a debugger to Tracker daemons Tracker daemons are not started directly. Instead they are started by the D-Bus -daemon by request. When using tracker-sandbox or the functional-tests, it's -difficult to start the daemon manually under `gdb`. +daemon by request. When using the run-uninstalled script or the +functional-tests, it's difficult to start the daemon manually under `gdb`. Instead, we recommend adding a 10 second timeout at the top of the daemon's main() function. In Vala code, try this: @@ -51,13 +51,12 @@ the 'Pausing' message, run the `gdb attach``command in another terminal within # Running Tracker daemons under Valgrind The Tracker daemons are launched using D-Bus autolaunch. When running them from -the source tree using tracker-sandbox or the functional tests, the commandline -is controlled by the D-Bus .service.in files stored in `./tests/services`. Just -change the `Exec=` line to add Valgrind, like this: +the source tree using the run-uninstalled script or the functional-tests, the +commandline is controlled by the D-Bus .service.in files stored in +`./tests/services`. Just change the `Exec=` line to add Valgrind, like this: Exec=/usr/bin/valgrind @abs_top_builddir@/src/tracker-store/tracker-store -By default the tracker-sandbox utility and the functional-tests will only -show output from Tracker code. For the functional-tests, set -TRACKER_TESTS_VERBOSE=1 to see output from Valgrind. For tracker-sandbox use -the `--debug-dbus` option. +By default the run-uninstalled script and the functional-tests will only show +output from Tracker code. For the functional-tests, set TRACKER_TESTS_VERBOSE=1 +to see output from Valgrind. For tracker-sandbox use the `--debug-dbus` option. |