Open manopapad opened 4 years ago
We don't provide debug symbols as they tend to be large and most people do not need them.
You should build the interpreter yourself. The recipe has tweak parameters for making debug builds but this stuff is new and seldom used.
I would support and effort to split debug info into separate packages for important packages though but we don't really have the tooling in place for that.
@mingwandroid I am trying to build the python interpreter myself but build_locally.py does not support building natively on ubuntu. Could you please suggest some resources related to building the python interpreter on ubuntu?
@mingwandroid I'm in the same boat and would like to have debug symbol support as well. Can you point us to any resources to help build the package locally?
I am trying to debug a C++ application that embeds a python interpreter, and would like to use gdb's python extensions to interpret python frames (
py-bt
,py-up
etc.). The version of gdb I get from conda-forge (conda install gdb
) is already properly configured to do this, and works for scripts executed in a standalone python interpreter. However, it doesn't work for applications that invoke the python interpreter throughlibpython.so
, and this is likely because the version oflibpython.so
I get from conda-forge does not seem to contain debug symbols (see command log below). Is it possible to update the recipes to include debug symbols forlibpython.so
as well?Note that I can get debug symbols on both the standalone and embedded interpreter cases if I use the debug builds from Ubuntu package
python-dbg
.Commands to reproduce:
Environment (
conda list
):Details about
conda
and system (conda info
):