Community
Participate
Working Groups
There is a warning marker in my project and once in a while the launch fails because of the following NPE. java.lang.NullPointerException at org.eclipse.cdt.launch.AbstractCLaunchDelegate.existsErrors(AbstractCLaunchDelegate.java:751) at org.eclipse.cdt.launch.AbstractCLaunchDelegate.finalLaunchCheck(AbstractCLaunchDelegate.java:700) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:836) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:705) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
*** Bug 278203 has been marked as a duplicate of this bug. ***
Given the impact on the issue, shouldn't we raise this to a P2? / Johan
Created attachment 137786 [details] fix npe Allow for attribute to be NULL.
Fixed in HEAD, now checks to see if the severity attribute is NULL. MIkhail, does this look right to you?
Ken, it seems to be caused by a race condition which is very difficult to catch - when I set breakpoints it works fine. I don't think it is worth to try to fix it "properly", so this solution is acceptable.