summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING14
1 files changed, 14 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index f951205e..b5c9c81c 100644
--- a/HACKING
+++ b/HACKING
@@ -8,6 +8,20 @@ debugging
* You can use the GI_SCANNER_DEBUG environment variable; see utils.py
for a list of debug flags.
+* It is possible to debug the various g-ir-* tools using PyDev's remote debugger.
+ To do this:
+ - locate the directory that contains the pydevd.py file matching the PyDev version
+ running in your Eclipse instance. This might look like:
+ /usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev_4.0.0.201505131500/pysrc/)
+ - open the "Debug" perspective in your Eclipse instance, open the "PyDev" menu and start the
+ debug server
+ - execute the g-ir-* tool setting the GI_SCANNER_DEBUG and PYDEVDPATH environment variables.
+ For example:
+ GI_SCANNER_DEBUG="pydevd" PYDEVDPATH="/usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev_4.0.0.201505131500/pysrc/" g-ir-scanner <parameters>
+ - In the example above, the PyDev debugger will run g-ir-scanner and stop execution in the main
+ script. You can then set extra breakpoints, step through the code, inspect variables at the
+ current scope, inspect the stack and so forth.
+
giscanner
---------