Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360910 - [compiler][resource] Resource leak warnings on throw statements which are not method exit points
Summary: [compiler][resource] Resource leak warnings on throw statements which are not...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-14 01:36 EDT by Deepak Azad CLA
Modified: 2019-10-08 14:27 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Deepak Azad CLA 2011-10-14 01:36:02 EDT
Kind of similar to the test case from bug 359334 comment 6.

The throw statements inside the try blocks are not method exit points as the exceptions are caught. (Test case from bug 359334 comment 6 works fine though)

----------------------------------------------------------------------------
protected void buildANTScript(String name) throws IOException {
	OutputStream outputStream = new FileOutputStream(name);

	try {
		if (name.length() > 10)
			throw new IOException();      // incorrect warning
	} catch (IOException ex) {
		throw ex;
	}

	try {
		System.out.println(outputStream);
		throw new NullPointerException();    // incorrect warning
	} catch (NullPointerException npe) {
		throw npe;
	}
}
----------------------------------------------------------------------------
Comment 1 Eclipse Genie CLA 2019-10-08 14:27:04 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.