No gdb debugging symbol table files #2236
Comments
|
I’m not vey familar with GDB’s Python extensions. Does it work if you use a plain virtualenv? How did you set up your development environment before adopting Pipenv? Maybe we can find out what Pipenv does wrong by comparing the two approaches. |
|
Well I need to rebuild my python from the ABS (on ArchLinux there are no debug packages), after that I will run into whats basically described over at pypa/virtualenv#644. However I was under the impression that |
|
If I understand correctly, this happens in a pipenv: and this happens outside of a pipenv: I assume that pipenv does not copy the necessary GDB scripts to the newly created virtualenvs and therefore GDB needs to load them from their original locations. This can be achieved by using a symlinked Python executable from within a virtualenv. GDB uses full path to the executable, after following symlinks, to construct the path to the required GDB script. That is why you see GDB attempting to load a file from a strange path If symlinks are not an option, you can copy the GDB scripts to the locations where GDB expects to find them. You may also modify |
|
I’m a bit torned on deciding whether this should be classified as an upstream issue. Maybe virtualenv (and the built-in venv) should be responsible for this. Do they have this problem on their own? (I image they do.) What do their maintainers have to say on this issue? |
So the problem is that I am unable to use
gdbhelper functions likepy-btwithpipenvprojects.Basically:
From within a project with
pipenv shell.Pipenv details
Please run
$ python -m pipenv.help, and paste the results here.$ python -m pipenv.help output
Pipenv version:
'2018.05.18'Pipenv location:
'/usr/lib/python3.6/site-packages/pipenv'Python location:
'/bin/python'Other Python installations in
PATH:2.7:/bin/python2.72.7:/bin/python2.72.7:/usr/bin/python2.73.6:/bin/python3.6m3.6:/bin/python3.63.6:/usr/bin/python3.63.6.5:/bin/python3.6.5:/usr/bin/python2.7.15:/bin/python22.7.15:/usr/bin/python23.6.5:/bin/python33.6.5:/usr/bin/python3PEP 508 Information:
System environment variables:
XDG_SEAT_PATHXDG_CONFIG_DIRSLANGDISPLAYSHLVLLOGNAMEXDG_VTNRLANGUAGEPWDMOZ_PLUGIN_PATHXDG_GREETER_DATA_DIRMAVEN_OPTSXAUTHORITYXDG_DATA_HOMEXDG_SESSION_IDGTK2_RC_FILESDESKTOP_SESSIONXDG_SESSION_DESKTOPGDMSESSIONCOLORTERMDBUS_SESSION_BUS_ADDRESSVTE_VERSIONMAILXDG_DATA_DIRS__LXSESSION_PIDXDG_MENU_PREFIXSHELLXDG_CONFIG_HOMESAL_USE_VCLPLUGINXDG_SESSION_TYPETERMGTK_MODULESXDG_CURRENT_DESKTOPPATHHOMEXDG_SEATTILIX_IDUSERXDG_RUNTIME_DIRXDG_SESSION_PATHOLDPWDPAGERLESSLESSCHARSETLESS_TERMCAP_mbLESS_TERMCAP_mdLESS_TERMCAP_meLESS_TERMCAP_seLESS_TERMCAP_soLESS_TERMCAP_ueLESS_TERMCAP_usLSCOLORSGOPATHGOBINCORRECT_IGNORECORRECT_IGNORE_FILEWORDCHARSHISTFILEHISTSIZESAVEHISTLISTMAXINTERACTIVE_FILTERDOTPATHSSH_AUTH_SOCKSSH_AGENT_PIDLS_COLORSEDITORuseridgroupidGOCACHEWORKON_HOME_VIRTUALENVWRAPPER_APIVIRTUALENVWRAPPER_SCRIPTUSE_CCACHEPACMAN_SILENT_JAVA_OPTIONSJAVA_FONTSMPD_HOSTWINEPREFIXWINEARCHQT_QPA_PLATFORMTHEMEQT_AUTO_SCREEN_SCALE_FACTORLDUSE_HOST_LEX_JAVA_AWT_WM_NONREPARENTINGGPG_TTYDOCKER_ID_USERINFINALITY_FT_BRIGHTNESSINFINALITY_FT_FILTER_PARAMSLD_LIBRARY_PATHC_INCLUDE_PATHCPLUS_INCLUDE_PATHCPATHPYTHONPATHZPLUG_ROOTPERIODFPATHZPLUG_HOMEZPLUG_THREADSZPLUG_PROTOCOLZPLUG_FILTERZPLUG_LOADFILEZPLUG_USE_CACHEZPLUG_ERROR_LOGZPLUG_BINZPLUG_CACHE_DIRZPLUG_REPOS_ZPLUG_VERSION_ZPLUG_URL_ZPLUG_OHMYZSH_ZPLUG_PREZTO_ZPLUG_AWKPATH_ZPLUG_CONFIG_SUBSHELLNVM_LAZY_LOADNVM_DIRENHANCD_DIRENHANCD_DISABLE_DOTENHANCD_DISABLE_HYPHENENHANCD_DISABLE_HOMEENHANCD_DOT_ARGENHANCD_HYPHEN_ARGENHANCD_HOME_ARGENHANCD_DOT_SHOW_FULLPATHENHANCD_USE_FUZZY_MATCHENHANCD_ROOTENHANCD_COMMANDENHANCD_FILTERGIT_FZFFZF_DEFAULT_OPTSZSHZSH_CACHE_DIRLC_ALLLC_CTYPEPYTHONDONTWRITEBYTECODEPIP_PYTHON_PATHPipenv–specific environment variables:
Debug–specific environment variables:
PATH:$HOME/.zplug/bin:/bin:$HOME/Git/Github/Dotfiles/Scripts:$HOME/.node_modules/bin:$HOME/.local/bin:$HOME/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/opt/cxoffice/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:$HOME/.rvm/bin:$HOME/.local/bin/gitHelpers:$HOME/.local/bin/droidHelpers:$HOME/.local/bin/dockerHelpers:$HOME/.local/bin/shellHelpers:$HOME/.local/bin/fileHelpers:$HOME/.local/bin/webHelpers:$HOME/.local/bin/installHelpers:$HOME/.cargo/bin:$HOME/.go/bin:$HOME/Git/Github/Linux/xmr-stak-cpu/bin:/var/lib/snapd/snap/bin:/$HOME/.gem/ruby/2.4.0/bin:$HOME/LabWork/IITB/Icover:/root/.gem/ruby/2.2.0/bin:$HOME/Matlab/MATLAB_Production_Server/R2015a/bin:$HOME/.gem/ruby/2.2.0/bin:$HOME/.gem/ruby/2.3.0/bin:/opt/schrodinger2016-2:$HOME/Git/Github/mylammps/src:$HOME/Git/Github/espresso/build:$HOME/Git/Github/Scripts/Build:$HOME/Git/Github/Scripts/System:$HOME/.local/g16:/usr/local/MATLAB/R2017a/binSHELL:/bin/zshEDITOR:nvimLANG:en_US.UTF-8PWD:$HOME/.virtualenvs/pyProj-UoyQSP0ZExpected result
I expected the stack trace. Or atleast recognition of the command.
Basically something like:
Actual result
So the actual result is already above.
Additional information pertaining to this is:
Pipenv output
Expected Output
Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
Pipfile
Commands
$ pipenv --two # Not really necessary here $ pipenv install numpy scipy $ gdb >>> py-bt >>> py-listThe text was updated successfully, but these errors were encountered: