#570: Remote Debugger - enhancements to integrate
--------------------------+----------------------
Reporter: rchyla | Owner: rchyla
Type: enhancement | Status: assigned
Priority: major | Milestone:
Component: *general* | Version:
Resolution: | Keywords:
--------------------------+----------------------
Changes (by simko):
* status: in_merge => assigned
Comment:
Thanks for the squash. There remained some cosmetics, so I have
replaced CDS Invenio by Invenio, fixed copyright years, deleted
trailing whitespace, replaced CRLF by Unix standards, removed
`CFG_REMOTE_DEBUGGER` stuff from `invenio.conf` (it was ignored, and
more variables would have to be put there like the winpdb password in
order to be complete, and inveniocfg would have to be updated for the
pathname list treatment, etc, so I think it is better to have nothing
in `invenio.conf` at the moment rather than being incomplete, since
developers can edit the concerned remote debugger file directly
anyway.) I'll send you my updates separately by mail.
However, winpdb does not seem to be able to attach for me when using
`debug=1`. While if I use our "traditional" approach:
{{{
import rpdb2; rpdb2.start_embedded_debugger('password')
}}}
as outlined in
[[https://twiki.cern.ch/twiki/bin/view/CDS/PythonAndApache#4_Debugging_mod_python_apps]],
then things work fine and winpdb attaches fine.
I have not tried to debug why it does not work for me. Does `debug=1`
work for you out of the box? If yes, then can we have a look
together?
--
Ticket URL: <http://invenio-software.org/ticket/570#comment:4>
Invenio <http://invenio-software.org>
