Skip to main content


Eclipse Community Forums

      Home
Home » Language IDEs » Java Development Tools (JDT) » Bug in org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsAction?
Bug in org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsAction? [message #212264] Fri, 12 August 2005 11:38 Go to next message
Eclipse UserFriend
Hi

I develope a plugin for automated debugging of java programs for
eclipse. My plugin launches several tests in an additional vm and use
the tools of eclipse to set breakpoints etc.

During the execution of my tool i get the following error:

--------------------------
!ENTRY org.eclipse.ui 4 0 2005-08-12 17:08:52.535
!MESSAGE Failed to execute runnable
(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
at org.eclipse.swt.SWT.error(SWT.java:2942)
at org.eclipse.swt.SWT.error(SWT.java:2865)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null
argument;
at org.eclipse.jface.util.Assert.isNotNull(Assert.java:149)
at org.eclipse.jface.util.Assert.isNotNull(Assert.java:125)
at
org.eclipse.jface.viewers.StructuredSelection.<init>(StructuredSelection.java:66)
at
org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsA ction$1.run(ShowSystemThreadsAction.java:103)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
... 18 more
--------------------------

I debugged the application and found that in ShowSystemThreadsAction at
line 102 the top stack frame of the current thread will assigned to the
variable tos. After that this frame should present to the user with a
StructuredSelection. But unfortunately the method getTopStackFrame can
return null. This cause an AssertionFailedException in the constructor
of the StructuredSelection.

Code snippet from ShowSystemThreadsAction (line 102-103):
tos = thread.getTopStackFrame();
getStructuredViewer().setSelection(new StructuredSelection(tos));

Can it be that this is a bug from the eclipse workbench? It is necessary
to check that the top stack frame is not null before the
StructuredSelction will be initialised?

The exception affect not the execution of my plugin. But the effect that
the error will displayed in the error log isn't very fine for me. The
consequence of this exception is still an unhandeld event loop exception
which will already logged in the error log.

FYI:
I use eclipse 3.1. The bug occurs on the windows, linux and mac machines.
Re: Bug in org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsAction? [message #212272 is a reply to message #212264] Fri, 12 August 2005 11:43 Go to previous messageGo to next message
Eclipse UserFriend
If you can provide a test case and the stack traces you provide here it
would be great if you would log a bug report against JDT Debug

Thanks
Darins

"Karsten Lehmann" <KarstenLehmann@web.de> wrote in message
news:ddifpr$gj4$1@news.eclipse.org...
> Hi
>
> I develope a plugin for automated debugging of java programs for
> eclipse. My plugin launches several tests in an additional vm and use
> the tools of eclipse to set breakpoints etc.
>
> During the execution of my tool i get the following error:
>
> --------------------------
> !ENTRY org.eclipse.ui 4 0 2005-08-12 17:08:52.535
> !MESSAGE Failed to execute runnable
> (org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable
> (org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
> at org.eclipse.swt.SWT.error(SWT.java:2942)
> at org.eclipse.swt.SWT.error(SWT.java:2865)
> at
>
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
> at
>
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
> at
>
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
java:226)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
..java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> at org.eclipse.core.launcher.Main.run(Main.java:973)
> at org.eclipse.core.launcher.Main.main(Main.java:948)
> Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null
> argument;
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:149)
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:125)
> at
>
org.eclipse.jface.viewers.StructuredSelection.<init>(StructuredSelection.jav
a:66)
> at
>
org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsA ction$1.run(Show
SystemThreadsAction.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
>
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
> ... 18 more
> --------------------------
>
> I debugged the application and found that in ShowSystemThreadsAction at
> line 102 the top stack frame of the current thread will assigned to the
> variable tos. After that this frame should present to the user with a
> StructuredSelection. But unfortunately the method getTopStackFrame can
> return null. This cause an AssertionFailedException in the constructor
> of the StructuredSelection.
>
> Code snippet from ShowSystemThreadsAction (line 102-103):
> tos = thread.getTopStackFrame();
> getStructuredViewer().setSelection(new StructuredSelection(tos));
>
> Can it be that this is a bug from the eclipse workbench? It is necessary
> to check that the top stack frame is not null before the
> StructuredSelction will be initialised?
>
> The exception affect not the execution of my plugin. But the effect that
> the error will displayed in the error log isn't very fine for me. The
> consequence of this exception is still an unhandeld event loop exception
> which will already logged in the error log.
>
> FYI:
> I use eclipse 3.1. The bug occurs on the windows, linux and mac machines.
Re: Bug in org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsAction? [message #212296 is a reply to message #212272] Fri, 12 August 2005 11:56 Go to previous messageGo to next message
Eclipse UserFriend
Sorry

Because my plugin is yet not public i cannot provide a special test
case. But if you inspect the code at my given position under the fact
that the method getTopStackFrame can return null i be sure that this is
a bug.

Should i always enter it as bug report if i cannot give a detailed test
case?

Best regards

Karsten

Darin Swanson schrieb:
> If you can provide a test case and the stack traces you provide here it
> would be great if you would log a bug report against JDT Debug
>
> Thanks
> Darins
>
> "Karsten Lehmann" <KarstenLehmann@web.de> wrote in message
> news:ddifpr$gj4$1@news.eclipse.org...
>
>>Hi
>>
>>I develope a plugin for automated debugging of java programs for
>>eclipse. My plugin launches several tests in an additional vm and use
>>the tools of eclipse to set breakpoints etc.
>>
>>During the execution of my tool i get the following error:
>>
>>--------------------------
>>!ENTRY org.eclipse.ui 4 0 2005-08-12 17:08:52.535
>>!MESSAGE Failed to execute runnable
>>(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
>>!STACK 0
>>org.eclipse.swt.SWTException: Failed to execute runnable
>>(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
>>at org.eclipse.swt.SWT.error(SWT.java:2942)
>>at org.eclipse.swt.SWT.error(SWT.java:2865)
>>at
>>
>
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
>
>>at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
>>at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
>>at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
>>at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
>>at
>>
>
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
>
>>at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
>>at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
>>at
>>
>
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
> java:226)
>
>>at
>>
>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
>
>>at
>>
>
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
>
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
> )
>
>>at
>>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
> .java:25)
>
>>at java.lang.reflect.Method.invoke(Method.java:324)
>>at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
>>at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
>>at org.eclipse.core.launcher.Main.run(Main.java:973)
>>at org.eclipse.core.launcher.Main.main(Main.java:948)
>>Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null
>>argument;
>>at org.eclipse.jface.util.Assert.isNotNull(Assert.java:149)
>>at org.eclipse.jface.util.Assert.isNotNull(Assert.java:125)
>>at
>>
>
> org.eclipse.jface.viewers.StructuredSelection.<init>(StructuredSelection.jav
> a:66)
>
>>at
>>
>
> org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsA ction$1.run(Show
> SystemThreadsAction.java:103)
>
>>at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
>>at
>>
>
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
>
>>... 18 more
>>--------------------------
>>
>>I debugged the application and found that in ShowSystemThreadsAction at
>>line 102 the top stack frame of the current thread will assigned to the
>>variable tos. After that this frame should present to the user with a
>>StructuredSelection. But unfortunately the method getTopStackFrame can
>>return null. This cause an AssertionFailedException in the constructor
>>of the StructuredSelection.
>>
>>Code snippet from ShowSystemThreadsAction (line 102-103):
>> tos = thread.getTopStackFrame();
>> getStructuredViewer().setSelection(new StructuredSelection(tos));
>>
>>Can it be that this is a bug from the eclipse workbench? It is necessary
>>to check that the top stack frame is not null before the
>>StructuredSelction will be initialised?
>>
>>The exception affect not the execution of my plugin. But the effect that
>>the error will displayed in the error log isn't very fine for me. The
>>consequence of this exception is still an unhandeld event loop exception
>>which will already logged in the error log.
>>
>>FYI:
>>I use eclipse 3.1. The bug occurs on the windows, linux and mac machines.
>
>
>
Re: Bug in org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsAction? [message #212303 is a reply to message #212296] Fri, 12 August 2005 12:01 Go to previous message
Eclipse UserFriend
Yes please still enter the bug report

"Karsten Lehmann" <KarstenLehmann@web.de> wrote in message
news:ddigrd$hnj$1@news.eclipse.org...
> Sorry
>
> Because my plugin is yet not public i cannot provide a special test
> case. But if you inspect the code at my given position under the fact
> that the method getTopStackFrame can return null i be sure that this is
> a bug.
>
> Should i always enter it as bug report if i cannot give a detailed test
> case?
>
> Best regards
>
> Karsten
>
> Darin Swanson schrieb:
> > If you can provide a test case and the stack traces you provide here it
> > would be great if you would log a bug report against JDT Debug
> >
> > Thanks
> > Darins
> >
> > "Karsten Lehmann" <KarstenLehmann@web.de> wrote in message
> > news:ddifpr$gj4$1@news.eclipse.org...
> >
> >>Hi
> >>
> >>I develope a plugin for automated debugging of java programs for
> >>eclipse. My plugin launches several tests in an additional vm and use
> >>the tools of eclipse to set breakpoints etc.
> >>
> >>During the execution of my tool i get the following error:
> >>
> >>--------------------------
> >>!ENTRY org.eclipse.ui 4 0 2005-08-12 17:08:52.535
> >>!MESSAGE Failed to execute runnable
> >>(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
> >>!STACK 0
> >>org.eclipse.swt.SWTException: Failed to execute runnable
> >>(org.eclipse.jface.util.Assert$AssertionFailedException: null argument;)
> >>at org.eclipse.swt.SWT.error(SWT.java:2942)
> >>at org.eclipse.swt.SWT.error(SWT.java:2865)
> >>at
> >>
> >
> >
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
> >
> >>at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2844)
> >>at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2575)
> >>at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
> >>at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
> >>at
> >>
> >
> >
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
> >
> >>at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
> >>at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
> >>at
> >>
> >
> >
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
> > java:226)
> >
> >>at
> >>
> >
> >
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
> >
> >>at
> >>
> >
> >
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> >
> >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>at
> >>
> >
> >
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
> > )
> >
> >>at
> >>
> >
> >
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
> > .java:25)
> >
> >>at java.lang.reflect.Method.invoke(Method.java:324)
> >>at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> >>at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> >>at org.eclipse.core.launcher.Main.run(Main.java:973)
> >>at org.eclipse.core.launcher.Main.main(Main.java:948)
> >>Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null
> >>argument;
> >>at org.eclipse.jface.util.Assert.isNotNull(Assert.java:149)
> >>at org.eclipse.jface.util.Assert.isNotNull(Assert.java:125)
> >>at
> >>
> >
> >
org.eclipse.jface.viewers.StructuredSelection.<init>(StructuredSelection.jav
> > a:66)
> >
> >>at
> >>
> >
> >
org.eclipse.jdt.internal.debug.ui.actions.ShowSystemThreadsA ction$1.run(Show
> > SystemThreadsAction.java:103)
> >
> >>at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> >>at
> >>
> >
> >
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
> >
> >>... 18 more
> >>--------------------------
> >>
> >>I debugged the application and found that in ShowSystemThreadsAction at
> >>line 102 the top stack frame of the current thread will assigned to the
> >>variable tos. After that this frame should present to the user with a
> >>StructuredSelection. But unfortunately the method getTopStackFrame can
> >>return null. This cause an AssertionFailedException in the constructor
> >>of the StructuredSelection.
> >>
> >>Code snippet from ShowSystemThreadsAction (line 102-103):
> >> tos = thread.getTopStackFrame();
> >> getStructuredViewer().setSelection(new StructuredSelection(tos));
> >>
> >>Can it be that this is a bug from the eclipse workbench? It is necessary
> >>to check that the top stack frame is not null before the
> >>StructuredSelction will be initialised?
> >>
> >>The exception affect not the execution of my plugin. But the effect that
> >>the error will displayed in the error log isn't very fine for me. The
> >>consequence of this exception is still an unhandeld event loop exception
> >>which will already logged in the error log.
> >>
> >>FYI:
> >>I use eclipse 3.1. The bug occurs on the windows, linux and mac
machines.
> >
> >
> >
Previous Topic:Skipping over app server generated code
Next Topic:Adding classpath entry to a JavaProject
Goto Forum:
  


Current Time: Sun Jul 20 12:49:52 EDT 2025

Powered by FUDForum. Page generated in 0.04092 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly