int19h ( Pavel Minaev )

Turns out this isn't a bug at all, but rather by design. The Textmate Python grammar assumes that r"" literals are mostly used for regex, and so it tries to highlight its contents as such; hence why the parentheses are of different color. If you put (?#foo) somewhere in the string, you'll see that it will be highlighted as a comment etc.

vsfeedback

comment created time in 2 days

PullRequestReviewEvent

issue commentmicrosoft/debugpy

notification like "Failed launch debugger for child process xxxx".

Thing is, child processes aren't supposed to start running anything until there's a debugger connection to them that has gone through the entire initialization stage (otherwise breakpoints might be skipped etc). So either the pool killing processes due to some kind of timeout, before they even had a chance to run anything; or there's some bug in how subprocesses are resumed.

liheyi360

comment created time in 2 days

issue commentmicrosoft/debugpy

When debugging stops in a "Subprocess", code is navigated to a strange read-only version of the current file

For "Attach to Process", you shouldn't need to import debugpy etc at all in your process - the whole point of that feature is that it injects the debugger without requiring the process to cooperate.

But once injected, it works the same as regular remote, so I don't think it'd make a difference in this case.

munael

comment created time in 2 days

PullRequestReviewEvent

issue commentmicrosoft/debugpy

Python extension sends "setPydevdSourceMap" when a ms-vscode.cpptools debugger is attached

This is not a debugpy issue, since debugpy doesn't send this message - only receives and processes it. The bug is in the code that sends it.

I left a comment on the original issue in vscode-jupyter with more details.

tjahn

comment created time in 3 days

issue closedmicrosoft/debugpy

Python extension sends "setPydevdSourceMap" when a ms-vscode.cpptools debugger is attached

Hello,

some time ago I started to experience a problme when debugging my C++ / Python project with VSCodes C++ debugger (sadly I do not know, when this problem arose). I already brought the bug up in microsoft/vscode-cpptools#8115 and microsoft/vscode-jupyter#7480, but both maintainers do not think that the bug is on their side.

Description

VSCode interactive Python crashes when trying to run cells after attaching the ms-vscode.cpptools C++ debugger to the Python process.

I develop a Python extension in C++. For debugging I start my python script with vscode using the interactive cell mode, attach the C++ debugger from the ms-vscode.cpptools extension to the process and then start calling cells. This worked until some weeks ago (though I do not know which extension versions I used back then).

Expected behaviour

I should be able to connect the C++ debugger from the microsoft/vscode-cpptools extension and use breakpoints etc in my C++ module, even when running it in the interactive Python process started by vscode.

Actual behaviour

As soon as the next interactive Python cell is run from vscode the interactive Python session crashes. The attached C++ debugger also crashes with the following message in VSCodes Debug Console:

Stopping due to fatal error: InvalidOperationException: No handler registered for request of type 'setPydevdSourceMap'!

I only found this message type in the microsoft/debugy repository and its predecessor.

Steps to reproduce:

Install the extensions ms-python.python and ms-vscode.cpptools.
create a Python script

# %% first run this cell to start the Python process and get its PID
import os
print(os.getpid())
# %% after attaching the debugger run this cell to trigger the error
print("test")

execute the first cell of the Python script in vscode interactively
attach you debugger to the printed pid using the following launch.json entry { "name": "(lldb) Attach Debugger", "type": "cppdbg", "request": "attach", "program": "/proc/${command:pickProcess}/exe", "processId": "${command:pickProcess}", "MIMode": "lldb", },
try executing the second cell after the debugger attached

Environment data

VSCode 1.60.0 on MacOS Big Sur 11.5.2
remote SSH server is an OpenSuse 15.2
ms-python.python@v2021.9.1191016588
ms-vscode.cpptools@v1.6.0.
debugpy version: 1.4.3 (in the .vscode-server/extensions/ms-python.*/...... directory)

closed time in 3 days

tjahn

issue commentmicrosoft/vscode-jupyter

Cant connect C++ debugger to interactive python session anymore

This is, indeed, a custom DAP message that debugpy handles. However, it is not sent by debugpy; it is sent by vscode-jupyter:

https://github.com/microsoft/vscode-jupyter/blob/38962619f8952b06b19b7932ec4380786e3c9ee9/src/client/datascience/jupyter/jupyterDebugger.ts#L94-L106

Thus the bug is that vscode-jupyter sends the message to the incorrect debug session - the C++ one, in this case.

And I'm not sure whether this has anything to do with the C++ session debugging the same process as the Python session. VSCode has a workflow where the user can start multiple unrelated but concurrent debug sessions. If this issue also repros in that scenario, it is a genuine bug - unrelated debug sessions shouldn't interfere with each other.

(Note, however, that even with that fix, it still wouldn't work, because debuggers generally need to assume full control of the process being debugged. So having two of them trying to independently control the same process will result in all kinds of breakage, possibly unreported.)

tjahn

comment created time in 3 days

push eventint19h/debugpy

Fabio Zadrozny

commit sha fdd1f4dc38342d6d2b3d5daf76db8dfa8e4cec99

When possible collect try..except information from source and not bytecode.