Repository navigation
Feature Request: Allow ignore exceptions from specific source #442
Description
Activity
heckerpowered We have already provided a user setting
java.debug.settings.exceptionBreakpoint.skipClassesto skip the specified classes when breaking on exceptions. Do you have a try on it?Hi heckerpowered, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
-
You can already specify exceptions to skip by class or package in your launch configuration using the
java.debug.settings.exceptionBreakpoint.skipClassessetting. For example:"configurations": [ { "type": "java", "name": "Debug (Launch)", …, "java.debug.settings.exceptionBreakpoint.skipClasses": [ "com.mycompany.game.MainLoop", "com.mycompany.game.internal.*" ] } ]
• See discussion in issue Add documentation for the supported launch/attach properties #412: UI for configuring step filters as workspace settings vscode-java-debug#412 (comment)
-
A dedicated feature to filter exceptions by name or package (for caught/uncaught breaks) is being tracked here: Allow to break on caught/uncaught exceptions by name or package namespace vscode-java-debug#1175
Other references with low confidence
- ignore unknown source in stepFilters (#757): explains that
stepFilterswon’t ignore exceptions from unknown sources. ignore unknown source in stepFilters vscode-java-debug#757 (comment) - Break on exception in Java for “just my code” (#756): similar request for Just My Code improvements;
stepFiltersis not sufficient for unknown source breaks. Break on exception in Java for “just my code” vscode-java-debug#756 (comment)
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
-
Some projects (such as games) will use try to catch exceptions in the main loop, which will cause the program to not generate uncaught exceptions, and if it breaks when an exception is caught, this will cause the debugger to break indefinitely (because exceptions are generated all the time and cannot be masked from the specified source)