This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 67
Breakpoints not working with remote debugging with handled exceptions #581
Comments
6 tasks
Does not repro on Windows or Linux. |
Please confirm that you can replicate it on Windows |
This is the same thing as #580 (that exception is considered unhandled even though it's handled because it's in the topmost frame during a remote attach), which is also probably why @karthiknadig is not being able to reproduce (it depends on whether it was started with the You can confirm that by putting the code inside a method:
|
fabioz
added a commit
to fabioz/ptvsd
that referenced
this issue
Sep 18, 2018
…n a remote attach. Fixes microsoft#580, microsoft#581
fabioz
added a commit
to fabioz/ptvsd
that referenced
this issue
Sep 20, 2018
…n a remote attach. Fixes microsoft#580, microsoft#581
fabioz
added a commit
to fabioz/ptvsd
that referenced
this issue
Sep 20, 2018
…n a remote attach. Fixes microsoft#580, microsoft#581
fabioz
added a commit
to fabioz/ptvsd
that referenced
this issue
Sep 20, 2018
…n a remote attach. Fixes microsoft#580, microsoft#581
fabioz
added a commit
to fabioz/ptvsd
that referenced
this issue
Sep 20, 2018
…n a remote attach. Fixes microsoft#580, microsoft#581
karthiknadig
pushed a commit
that referenced
this issue
Sep 24, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment data
Actual behavior
Debugger does not break at breakpoints when there's a handled exception.
Expected behavior
Debugger should break at breakpoints.
This used to work in
4.1.1a5
Steps to reproduce:
Breakpoints
of VSC are as follows (default):[ ] Raised Exceptions
[x] Uncaught Exceptions
time.sleep(1)
This seems to reproduce only when we have handled exceptions. So please look into this after resolving #580
The text was updated successfully, but these errors were encountered: