[Python-modules-team] Bug#868055: Bug#868055: virtualenv'ed python-dbg doesn't work smoothly with gdb (py- commands are gone)
Yaroslav Halchenko
debian at onerussian.com
Tue Jul 11 19:28:14 UTC 2017
On Tue, 11 Jul 2017, Yaroslav Halchenko wrote:
> Package: python-virtualenv
> Version: 15.1.0+ds-1
> Severity: normal
> Not 100% sure if it is not a python-dbg or gdb issue, but I think it might as
> well be virtualenv:
> $> virtualenv --python=/usr/bin/python-dbg venv-dbg
> Running virtualenv with interpreter /usr/bin/python-dbg
> New python executable in /tmp/venv-dbg/bin/python-dbg
> Also creating executable in /tmp/venv-dbg/bin/python
> [21403 refs]
> Installing setuptools, pkg_resources, pip, wheel...done.
> [47796 refs]
> $> gdb -q -ex 'py-bt' -ex quit /usr/bin/python-dbg
> Reading symbols from /usr/bin/python-dbg...done.
> Traceback (most recent call first):
> Python Exception <class 'gdb.error'> No frame is currently selected.:
> Error occurred in Python command: No frame is currently selected.
> $> gdb -q -ex 'py-bt' -ex quit $PWD/venv-dbg/bin/python-dbg
> Reading symbols from /tmp/venv-dbg/bin/python-dbg...done.
> Undefined command: "py-bt". Try "help".
ok -- the reason is that the corresponding python*-gdb.py (e.g.
/usr/share/gdb/auto-load/usr/bin/python3.5-gdb.py) is not copied over as
well under bin/ of the virtualenv where gdb also looks for it, and it
would also require add-auto-load-safe-path instruction to gdb (eg. via
-iex) to allow loading from it. May be there is another way also to
point to it -- didn't research yet
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
More information about the Python-modules-team
mailing list