Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337569

Summary:

Failures in OSGi tests for findEntries

Product:

[Eclipse Project] Equinox

Reporter:

Thomas Watson <tjwatson>

Component:

Framework

Assignee:

Thomas Watson <tjwatson>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

3.6

Target Milestone:

3.7 M6

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
possible fix	none

Description Thomas Watson

2011-02-18 09:11:26 EST

I think this is a consequence of the fix in bug 337370.

The following NPE failure is being reported in the N20110217-2000 build.

java.lang.NullPointerException
at org.eclipse.osgi.tests.bundles.BundleResourceTests.checkEntries(BundleResourceTests.java:109)
at org.eclipse.osgi.tests.bundles.BundleResourceTests.testBug328795(BundleResourceTests.java:79)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:416)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:249)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
at org.eclipse.core.launcher.Main.main(Main.java:34)

Comment 1 Thomas Watson

2011-02-18 10:54:01 EST

Created attachment 189285 [details]
possible fix

Looks like the optimization path does not handle escape characters correctly.  Instead of adding more code to the optimization path to handle the very rare case of input with an escape character I opted to avoid the optimization code path if an escape character is found.

Comment 2 Thomas Watson

2011-02-18 10:56:37 EST

Patch released.