Skip to content

debugging an exception causes my code to receive a terminate instead of stop event #1931

@LevoDeLellis

Description

@LevoDeLellis

I'm playing around with DAPs and I have a good understanding of it all and was able to set breakpoints and such.

For fun I ran code that hit an exception, the DAP prints the exception over stderr and sends a terminate event, I was expecting a stop event (reason: exception, desc: list index out of range).
I tried using wireshark to see what vscode does. I appear to be sending the same init and launch commands, the only difference I can see is how I launched debugpy and I doubt that's the problem? I wrote how vscode seems to launch. I tried doing the same thing below except I didn't use the same port and I don't use the access token flag. I doubt these could be the problem

Does anyone happen to know why I get the exception in stderr instead of a stop event?

/bin/python
-X
frozen_modules=off
/path/to/debugpy
--connect
127.0.0.1:53223
--configure-qt
none
--adapter-access-token
long-id

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions