Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on How to avoid "exception is never thrown" when commenting out a line while debugging

Post

How to avoid "exception is never thrown" when commenting out a line while debugging

+7
−1

I have a code block like this:

try {
    ...
    x.foo(); // This is the line that forces us to have the try block
    ...
} catch (ArrayIndexOutOfBoundsException e) {
    logger.error(e.getMessage(), e);
}

x.foo() is the line that is potentially throwing the exception.

Let's say that I am debugging the above block, and I want to comment out that line. What happens then is that I get this:

error: exception ArrayIndexOutOfBoundsException is never thrown in
       body of corresponding try statement

My question is how to handle this in a convenient way while debugging. I know how to rewrite it properly when I'm done debugging. But it is extremely annoying to to repeatedly remove and restore the try and catch lines just because I want to temporarily disable a line.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

May I suggest you to change the exception type in your example? `ArrayIndexOutOfBoundsException` is a... (2 comments)
Step over (1 comment)
Step over
Alexei‭ wrote over 2 years ago

I am not working with a Java IDE, but I am wondering if you have the option to place a breakpoint for x.foo and step over it (might also work with dragging current execution point to a subsequent instruction).