The closest solution is rpdb2 -d, but that requires both an
interactive password prompt and a subsequent attach/go/detach. This
would be immensely useful for allowing arbitrary debugging of
long-running programs (especially if they're started
non-interactively), even in production.
Another nice feature, for additional security, is to use Unix sockets
instead of TCP sockets where available, since authentication is taken
care of by setting the permissions on the socket (no more passwords).
But for now, even localhost-only TCP listeners with empty passwords is
sufficient for our needs.
Thanks.
--
Yang Zhang
http://yz.mit.edu/
--
You received this message because you are subscribed to the Google Groups "Winpdb" group.
To post to this group, send email to win...@googlegroups.com.
To unsubscribe from this group, send email to winpdb+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/winpdb?hl=en.
Running setup.py egg_info for package rfoo
Unable to execute darcs -- if you are building a package with
'setup.py sdist', 'setup.py bdist_egg', or other package-building
commands, then the resulting package might be missing some files. If
you are not building a package then you can ignore this warning.
Installing collected packages: rfoo
Running setup.py install for rfoo
building 'rfoo.marsh' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/include/python2.6 -c rfoo/marsh.c -o
build/temp.linux-x86_64-2.6/rfoo/marsh.o
gcc: rfoo/marsh.c: No such file or directory
gcc: no input files
error: command 'gcc' failed with exit status 1
Complete output from command /home/yang/work/pod/env/bin/python -c
"import setuptools;
__file__='/home/yang/work/pod/env/build/rfoo/setup.py';
execfile('/home/yang/work/pod/env/build/rfoo/setup.py')" install
--single-version-externally-managed --record
/tmp/pip-ABCj7V-record/install-record.txt --install-headers
/home/yang/work/pod/env/include/site/python2.6:
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.6
creating build/lib.linux-x86_64-2.6/rfoo
copying rfoo/__init__.py -> build/lib.linux-x86_64-2.6/rfoo
copying rfoo/_rfoo.py -> build/lib.linux-x86_64-2.6/rfoo
creating build/lib.linux-x86_64-2.6/rfoo/utils
copying rfoo/utils/__init__.py -> build/lib.linux-x86_64-2.6/rfoo/utils
copying rfoo/utils/rconsole.py -> build/lib.linux-x86_64-2.6/rfoo/utils
running build_ext
building 'rfoo.marsh' extension
creating build/temp.linux-x86_64-2.6
creating build/temp.linux-x86_64-2.6/rfoo
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/include/python2.6 -c rfoo/marsh.c -o
build/temp.linux-x86_64-2.6/rfoo/marsh.o
gcc: rfoo/marsh.c: No such file or directory
gcc: no input files
error: command 'gcc' failed with exit status 1
----------------------------------------
Command /home/yang/work/pod/env/bin/python -c "import setuptools;
__file__='/home/yang/work/pod/env/build/rfoo/setup.py';
execfile('/home/yang/work/pod/env/build/rfoo/setup.py')" install
--single-version-externally-managed --record
/tmp/pip-ABCj7V-record/install-record.txt --install-headers
/home/yang/work/pod/env/include/site/python2.6 failed with error code
1
Storing complete log in /home/yang/.pip/pip.log
Strangely, running `python setup.py build` manually works, but not
`pip install rfoo`. Any ideas on why?
I tried using it, and it works nicely as advertised, but currently
browsing things feels cumbersome. I have no global variables to
directly inspect from the rconsole thread, so I need to traverse frame
objects and look at their f_locals (at least with debuggers, I have
a smoother experience jumping around frames and whatnot).
Do you have any tips on how to effectively inspect/debug code from rconsole?
Thanks,
Yang