vscode: Exception information is not accessible

  • VSCode Version: 1.48.2 (system setup)
  • OS Version: Microsoft Windows [Version 10.0.19041.450]

Steps to Reproduce:

  1. Open a workspace that contains code with problems.
  2. Run the code in debug mode.
  3. When debugging stops and issues are found, try using F8 / Shift+F8 to navigate between them.
  4. Navigation sometimes works, but often doesn’t. It seems like, once navigation has stopped working, that’s it gone until code is restarted.
  • I am debugging a fairly complex Python project that I’m unfortunately unable to share (it’s a university assignment), but it’s based on the Flatland Challenge.
  • It has occurred to me that the issue may be to do with our evaluation script spawning a window in which to visualize the simulation.
  • I am running VS Code with editor accessibility on and NVDA.
  • The exceptions also don’t seem to be added to the problems area, so I can find no way to read them, which makes things … difficult.

Does this issue occur when all extensions are disabled?: Not applicable

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 19 (11 by maintainers)

Commits related to this issue

Most upvoted comments

Exception information is now accessible. I have changed the following:

  1. Once an exception happens while debugging focused is passed to the exception widget
  2. Exception widget aria labale contains the exception details including the stack trace
  3. You can close the exception widget via Esc

@SaschaCowley try it out and let us know what you think. Thanks!