-
Hi all, glad this extension exists! So I just gave it a first go with a helloworld.cpp and the tasks.json/launch.json stuff set up, and here's the Debug Console print in full:
Well, there's our hello-world output, so for the actual use case it works perfectly well here with gdb. No complaints! Just idly wondering about all the noise above that. Wonder if known, or bug, or my-local-setup-borked with respect to something Pythonic. (I never keep track of Python versions and libs on my system, since I don't Py dev myself. Some other packages I install on my Linux also install Python stuff, and their updates bring in Python-related updates, laggily.) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This seems "local setup specific". The warning is about the used python library (pretty printers are loaded with the python library GDB is linked against and found on the system) 3.6+ and installed pretty printers that are used by GDB but not match this. I'd suggest to recheck if there are any outstanding system updates, then check with |
Beta Was this translation helpful? Give feedback.
This seems "local setup specific". The warning is about the used python library (pretty printers are loaded with the python library GDB is linked against and found on the system) 3.6+ and installed pretty printers that are used by GDB but not match this.
I'd suggest to recheck if there are any outstanding system updates, then check with
ldd $(which gdb)
which python library is used - it should be the system one under/usr/lib
. If this isn't the case then you can create a gdb.sh wrapper script which setsLD_LIBRARY_PATH
or possibly evenLD_PRELOAD
to point to the right library, then executesgdb $*
, then choose that wrapper asgdbpath
for this extension - or otherwise ensure that the syste…