Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Double-click to set breakpoint?

Double-click to set breakpoint? [message #254471]

Tue, 01 July 2008 16:24

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Has something intentionally changed in 3.4 so that you can no longer
toggle a breakpoint by double-clicking in the annotation area to the
left of the code in the Java editor? I don't remember seeing anything in
the New & Noteworthy about it, but perhaps I missed something...

Eric

Re: Double-click to set breakpoint? [message #254476 is a reply to message #254471]

Tue, 01 July 2008 16:35

Eclipse User

Eric,
Dbl clicking to toggle a breakpoint is working for me in 3.4

Darins
http://runnerwhocodes.blogspot.com

"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:g4e3qk$uie$1@build.eclipse.org...
> Has something intentionally changed in 3.4 so that you can no longer
> toggle a breakpoint by double-clicking in the annotation area to the left
> of the code in the Java editor? I don't remember seeing anything in the
> New & Noteworthy about it, but perhaps I missed something...
>
> Eric

Re: Double-click to set breakpoint? [message #254480 is a reply to message #254476]

Tue, 01 July 2008 22:33

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Darin Swanson wrote:
> Eric,
> Dbl clicking to toggle a breakpoint is working for me in 3.4

That's not what I wanted to hear - now I have to narrow it down instead
of just being lazy and complaining ;-)

Here's the exception from Error Log whenever I try to toggle a
breakpoint via double-click. Is this enough for a Bugzilla? It doesn't
seem like it...

null
Error
Tue Jul 01 22:31:57 EDT 2008
Unhandled event loop exception

java.lang.NullPointerException
at
org.eclipse.ui.actions.ContributedAction.runWithEvent(Contri butedAction.java:181)
at org.eclipse.ui.internal.actions.CommandAction.run(CommandAct ion.java:171)
at
org.eclipse.ui.texteditor.AbstractTextEditor$14.triggerActio n(AbstractTextEditor.java:2890)
at
org.eclipse.ui.texteditor.AbstractTextEditor$14.mouseDoubleC lick(AbstractTextEditor.java:2915)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:183)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
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(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

> "Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
> news:g4e3qk$uie$1@build.eclipse.org...
>> Has something intentionally changed in 3.4 so that you can no longer
>> toggle a breakpoint by double-clicking in the annotation area to the left
>> of the code in the Java editor? I don't remember seeing anything in the
>> New & Noteworthy about it, but perhaps I missed something...
>>
>> Eric
>
>

Re: Double-click to set breakpoint? [message #254484 is a reply to message #254471]

Wed, 02 July 2008 03:20

Eclipse User

Originally posted by: mauro.molinari.cardinis.com

Eric Rizzo ha scritto:
> Has something intentionally changed in 3.4 so that you can no longer
> toggle a breakpoint by double-clicking in the annotation area to the
> left of the code in the Java editor? I don't remember seeing anything in
> the New & Noteworthy about it, but perhaps I missed something...

It happened to me for one class once... I couldn't understand why, but
after trying to set another breakpoint on another class, it worked, so I
thought it might have been because of Eclipse coulnd't set the
breakpoint on the first class (it was in a third-party library for which
I had the source, but I didn't know how it was compiled). Anyway, it
sounded strange to me because Eclipse didn't give any warning or error
message and because when debugging I could see the full stack traces
(with line numbers) for that class, too.

Mauro.

Re: Double-click to set breakpoint? [message #254488 is a reply to message #254480]

Wed, 02 July 2008 03:27

Eclipse User

Eric Rizzo wrote:
> Darin Swanson wrote:
>> Eric,
>> Dbl clicking to toggle a breakpoint is working for me in 3.4
>
> That's not what I wanted to hear - now I have to narrow it down
> instead of just being lazy and complaining ;-)
>
> Here's the exception from Error Log whenever I try to toggle a
> breakpoint via double-click. Is this enough for a Bugzilla? It doesn't
> seem like it...
Could be a corrupt install. Can you try with a new install (Into a new
directory)? Also, does it always happen? If you can reproduce with the
fresh install then please file a bug report with the steps to reproduce
the NPE.

Dani
>
> null
> Error
> Tue Jul 01 22:31:57 EDT 2008
> Unhandled event loop exception
>
> java.lang.NullPointerException
> at
> org.eclipse.ui.actions.ContributedAction.runWithEvent(Contri butedAction.java:181)
>
> at
> org.eclipse.ui.internal.actions.CommandAction.run(CommandAct ion.java:171)
> at
> org.eclipse.ui.texteditor.AbstractTextEditor$14.triggerActio n(AbstractTextEditor.java:2890)
>
> at
> org.eclipse.ui.texteditor.AbstractTextEditor$14.mouseDoubleC lick(AbstractTextEditor.java:2915)
>
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:183)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3823)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3422)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
>
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> 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(EclipseS tarter.java:382)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> 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:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>
>
>
>> "Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
>> news:g4e3qk$uie$1@build.eclipse.org...
>>> Has something intentionally changed in 3.4 so that you can no longer
>>> toggle a breakpoint by double-clicking in the annotation area to the
>>> left of the code in the Java editor? I don't remember seeing
>>> anything in the New & Noteworthy about it, but perhaps I missed
>>> something...
>>>
>>> Eric
>>
>>

Re: Double-click to set breakpoint? [message #254521 is a reply to message #254488]

Wed, 02 July 2008 10:38

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Daniel Megert wrote:
> Eric Rizzo wrote:
>> Darin Swanson wrote:
>>> Eric,
>>> Dbl clicking to toggle a breakpoint is working for me in 3.4
>>
>> That's not what I wanted to hear - now I have to narrow it down
>> instead of just being lazy and complaining ;-)
>>
>> Here's the exception from Error Log whenever I try to toggle a
>> breakpoint via double-click. Is this enough for a Bugzilla? It doesn't
>> seem like it...
> Could be a corrupt install. Can you try with a new install (Into a new
> directory)? Also, does it always happen? If you can reproduce with the
> fresh install then please file a bug report with the steps to reproduce
> the NPE.

I just installed yesterday. I added the Mylyn JIRA connector and JET
0.8, but other than that it is the RCP/Plugin Dev package.
It happens on all classes, both source in projects and libraries. I'll
try restarting and if it persists I'll enter a bug.

Eric

Re: Double-click to set breakpoint? [message #254541 is a reply to message #254521]

Wed, 02 July 2008 13:40

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Eric Rizzo wrote:
> Daniel Megert wrote:
>> Eric Rizzo wrote:
>>> Darin Swanson wrote:
>>>> Eric,
>>>> Dbl clicking to toggle a breakpoint is working for me in 3.4
>>>
>>> That's not what I wanted to hear - now I have to narrow it down
>>> instead of just being lazy and complaining ;-)
>>>
>>> Here's the exception from Error Log whenever I try to toggle a
>>> breakpoint via double-click. Is this enough for a Bugzilla? It
>>> doesn't seem like it...
>> Could be a corrupt install. Can you try with a new install (Into a new
>> directory)? Also, does it always happen? If you can reproduce with the
>> fresh install then please file a bug report with the steps to
>> reproduce the NPE.
>
> I just installed yesterday. I added the Mylyn JIRA connector and JET
> 0.8, but other than that it is the RCP/Plugin Dev package.
> It happens on all classes, both source in projects and libraries. I'll
> try restarting and if it persists I'll enter a bug.

Restarting Eclipse seems to have worked. Wish I could do more to track
it down, but its gone now.
Would there be any use in entering a bug report with the NPE stack trace
alone? Perhaps the code in that stack could be cleaned up to avoid such
problems in general...?

Eric

Re: Double-click to set breakpoint? [message #254627 is a reply to message #254541]

Wed, 02 July 2008 14:34

Eclipse User

"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:g4gehv$ua1$2@build.eclipse.org...
> Eric Rizzo wrote:
>> Daniel Megert wrote:
>>> Eric Rizzo wrote:
>>>> Darin Swanson wrote:
>>>>> Eric,
>>>>> Dbl clicking to toggle a breakpoint is working for me in 3.4
>>>>
>>>> That's not what I wanted to hear - now I have to narrow it down instead
>>>> of just being lazy and complaining ;-)
>>>>
>>>> Here's the exception from Error Log whenever I try to toggle a
>>>> breakpoint via double-click. Is this enough for a Bugzilla? It doesn't
>>>> seem like it...
>>> Could be a corrupt install. Can you try with a new install (Into a new
>>> directory)? Also, does it always happen? If you can reproduce with the
>>> fresh install then please file a bug report with the steps to reproduce
>>> the NPE.
>>
>> I just installed yesterday. I added the Mylyn JIRA connector and JET 0.8,
>> but other than that it is the RCP/Plugin Dev package.
>> It happens on all classes, both source in projects and libraries. I'll
>> try restarting and if it persists I'll enter a bug.
>
> Restarting Eclipse seems to have worked. Wish I could do more to track it
> down, but its gone now.
> Would there be any use in entering a bug report with the NPE stack trace
> alone? Perhaps the code in that stack could be cleaned up to avoid such
> problems in general...?
>
> Eric

I would log it against Platform UI so that ContributedAction can get a
review for the problem

Thanks
Darins
http://runnerwhocodes.blogspot.com

Re: Double-click to set breakpoint? [message #254632 is a reply to message #254627]

Wed, 02 July 2008 15:14

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=239317

Darin Swanson wrote:
> "Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
> news:g4gehv$ua1$2@build.eclipse.org...
>> Eric Rizzo wrote:
>>> Daniel Megert wrote:
>>>> Eric Rizzo wrote:
>>>>> Darin Swanson wrote:
>>>>>> Eric,
>>>>>> Dbl clicking to toggle a breakpoint is working for me in 3.4
>>>>> That's not what I wanted to hear - now I have to narrow it down instead
>>>>> of just being lazy and complaining ;-)
>>>>>
>>>>> Here's the exception from Error Log whenever I try to toggle a
>>>>> breakpoint via double-click. Is this enough for a Bugzilla? It doesn't
>>>>> seem like it...
>>>> Could be a corrupt install. Can you try with a new install (Into a new
>>>> directory)? Also, does it always happen? If you can reproduce with the
>>>> fresh install then please file a bug report with the steps to reproduce
>>>> the NPE.
>>> I just installed yesterday. I added the Mylyn JIRA connector and JET 0.8,
>>> but other than that it is the RCP/Plugin Dev package.
>>> It happens on all classes, both source in projects and libraries. I'll
>>> try restarting and if it persists I'll enter a bug.
>> Restarting Eclipse seems to have worked. Wish I could do more to track it
>> down, but its gone now.
>> Would there be any use in entering a bug report with the NPE stack trace
>> alone? Perhaps the code in that stack could be cleaned up to avoid such
>> problems in general...?
>>
>> Eric
>
> I would log it against Platform UI so that ContributedAction can get a
> review for the problem
>
> Thanks
> Darins
> http://runnerwhocodes.blogspot.com
>
>

Previous Topic:	Debugging suddenly became very slow
Next Topic:	How to listen for "Javadoc location" change

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 02 06:16:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter