pyuno: add some debugging hints
Change-Id: Id01e689911de8bc4402803e130db99b1b7c5b365
This commit is contained in:
parent
f6a74ce9bb
commit
7b08ccceff
1 changed files with 11 additions and 0 deletions
11
pyuno/README
11
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
|
Then you'll start to see your exceptions on the console instead of them getting
|
||||||
lost at the UNO interface.
|
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.
|
||||||
|
|
Loading…
Reference in a new issue