summaryrefslogtreecommitdiff
path: root/pyuno
diff options
context:
space:
mode:
authorMichael Stahl <mstahl@redhat.com>2016-03-22 21:53:23 +0100
committerMichael Stahl <mstahl@redhat.com>2016-03-23 15:51:50 +0100
commit7b08ccceffac5b5df904f84ca0b5aa646d6bd00e (patch)
tree514321db2bde1483c4210d09f3a5691cb3c83a15 /pyuno
parentf6a74ce9bbe4788fbeff463b52557b7e5aaa809f (diff)
pyuno: add some debugging hints
Change-Id: Id01e689911de8bc4402803e130db99b1b7c5b365
Diffstat (limited to 'pyuno')
-rw-r--r--pyuno/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/pyuno/README b/pyuno/README
index 1138ce7b284e..57f57db69870 100644
--- a/pyuno/README
+++ b/pyuno/README
@@ -6,3 +6,14 @@ To have much joy debugging python extensions you need to:
Then you'll start to see your exceptions on the console instead of them getting
lost at the UNO interface.
+
+Python also comes with a gdb script
+libpython$(PYTHON_VERSION_MAJOR).$(PYTHON_VERSION_MINOR)m.so-gdb.py
+that is copied to instdir and will be auto-loaded by gdb;
+it provides commands like "py-bt" to get a python-level backtrace,
+and "py-print" to print python variables.
+
+Another way to debug python code is to use pdb: edit some initalization
+function to to insert "import pdb; pdb.set_trace()" (somewhere so that it is
+executed early), then run soffice from a terminal and a command-line python
+debugger will appear where you can set python-level breakpoints.