Community
Participate
Working Groups
Build Identifier: 20110526-1053 eclipse.buildId=I20110519-1138 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.linuxtools.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.linuxtools.product Error Tue Jun 14 09:41:10 CEST 2011 An internal error occurred during: "Clear Breakpoints Status". java.lang.NullPointerException at org.eclipse.cdt.dsf.mi.service.MIBreakpointsManager$24$1.run(MIBreakpointsManager.java:1400) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.cdt.dsf.mi.service.MIBreakpointsManager$24.run(MIBreakpointsManager.java:1442) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Reproducible: Didn't try
Created attachment 203950 [details] Log file for the last couple of days. Shows errors for "Clear Breakpoints Status"
I get this same error frequently. I am unable to isolate why it occurs. I have attached my log file that shows the last few days of history. It contains multiple examples of the error. I am also attaching a screen shot of the threads as they show up in the Debug view; the state of that window look out-of-the-ordinary. Here is what I know: 1. Run debug configuration of the application. 2. The application's window opens (it is a GUI app using GLUT). 3. The application stops executing and no breakpoints are hit. 4. The threads in the Debug window do not show a call stack. There are three threads shown as part of the .exe process. The first two say "(Running: Container). The third threads says "(Running: User Request). The call stack is not displayed.
Created attachment 203951 [details] Screen shot of the Debug view just before error dialog opens.
I forgot to add steps 4 and 5 in the previous comment. 4. Click the red square to stop debugging. 5. My applications GUI window closes. 6. Eclipse opens a dialog box and explains "Clear Breakpoints Status" experienced a java null pointer exception. I was using at least one conditional breakpoint, but it is hard to tell if that was a factor in the dialog box opening.
*** This bug has been marked as a duplicate of bug 358754 ***