From 7b08ccceffac5b5df904f84ca0b5aa646d6bd00e Mon Sep 17 00:00:00 2001 From: Michael Stahl Date: Tue, 22 Mar 2016 21:53:23 +0100 Subject: pyuno: add some debugging hints Change-Id: Id01e689911de8bc4402803e130db99b1b7c5b365 --- pyuno/README | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'pyuno/README') 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. -- cgit