On running script, pausing to debug the program terminates silently without error whereever the program is paused but runs successfully otherwise via integrated terminal #1760
Comments
|
Also here is the log viewer entry specific to the systemd-coredump binary Process 11482 (python) of user 1000 dumped core. Module /home/john/.local/lib/python3.11/site-packages/Rtree.libs/libspatialindex-91fc2909.so.6.1.1 without build-id. Stack trace of thread 11497: Stack trace of thread 11500: Stack trace of thread 11498: Stack trace of thread 11501: Stack trace of thread 11517: |
|
Hi @makingglitches could you send me your launch.json config. Also could you try debugging using the new Python Debugger Extension in insiders to see if the error also occurs there? thank you so much. |
|
I'll see if the new one works, assuming there is one, but I had tried their pre-release version as well. I have been using the standard python debugger, no venv or other virtual environment therefore also no launch.json configuration, I just choose "launch python file" by default. |
|
With what i'm guessing is the new version of vs code effecting the display not the python debugger, I'm seeing the following. The invalid page exception is new, since I last touched this code, but I think that may be being caused by the addition of a faulty Rtree module i'm about to remove. Actually no, isn't that interesting, see next comment. |
|
when I allow the code to just run the page exception disappears as well. |
This comment has been minimized.
This comment has been minimized.
|
The callstacks look like a problem in CPython? I guess I'd just try the same thing with 3.13 instead of 3.11. Debugpy doesn't debug CPython itself, you'd need a C++ debugger for that. |
Here is the matching syslog entry for the core dump
Type: Bug
Behaviour
Expected vs. Actual
I am attempting to step through a python script I am writing, and when the debugger is paused the debugger is dying silently without any error or exception. In fact the code itself is not throwing an exception or error.
When click Run -> Start Debugging, the code executes as expected, but if there are any breakpoints and I pause for more than a moment Python crashes and a coredump log entry is placed in my system log.
However if there are no breakpoints, the code executes until it either encounters an error or completes successfully as expected via the same launch method.
This happens on the pre-release version and v2023.20.0 of the Python Extension.
UPDATE: It was my feeling this was something that has a multi-threaded aspect to it. I am presently debugging single threaded code with no cpython component to it and its pausing just fine using the standard python libraries.
To provide justication to NOT just bin this bug and say "oh it relates to third party things". please note the libs being used are GDAL AND RTREE. Two STANDARD GIS related projects that are pretty much universally accepted , since geopandas sucks for example. And also its more about catching failures in cpython and thread problems which should be able to be debugged or the problems detected with them. Also the ecosystem of tools cannot be said to work if some very common pieces break. Swig is pretty much accepted, cpython is integral, and there are some really specific scenarios being represented here where the user cannot debug why multi threading in native bindings are working fine when the code is just run but dying on them randomly otherwise. Rather than create some fat ugly female weirdo to represent me at this stage of learning and fuck me out of time, why not just fix the problem and move you asshats.
Steps to reproduce:
Diagnostic data
python.languageServersetting: DefaultOutput for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)User Settings
Extension version: 2023.20.0
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:50:47.800Z)
OS version: Linux x64 6.5.12-200.fc38.x86_64
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: