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

Bug 80654

Summary: [breakpoints] Breakpoint location verification
Product: [Eclipse Project] Platform Reporter: Darin Swanson <Darin_Swanson>
Component: AntAssignee: Platform-Ant-Inbox <platform-ant-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: Michael_Rennie, sja.eclipse
Version: 3.1Keywords: usability
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Ant UI patch to provide the start of breakpoint location verification none

Description Darin Swanson CLA 2004-12-09 17:24:42 EST 
When tasks are declared over multiple lines, a breakpoint will only work on 
the end line of the declaration.

Screams that we need a breakpoint location verifier for the Ant editor
Comment 1 Darin Swanson CLA 2004-12-13 23:37:45 EST 
Created attachment 16572 [details]
Ant UI patch to provide the start of breakpoint location verification
Comment 2 Darin Swanson CLA 2005-03-21 23:01:47 EST 
Deferred
Comment 3 Darin Swanson CLA 2006-08-24 14:16:46 EDT 
*** Bug 155082 has been marked as a duplicate of this bug. ***
Comment 4 Simon Archer CLA 2006-08-24 14:21:27 EDT 
Here are the comments from bug 155082, which has been marked as a duplicate of this bug.  I feel these comments might get lost and will be worth condsidering when this bug gets assigned.

Consider the following test script.  I placed breakpoints on every line within
the <project> element.  The script has been annotated to show the lines at
which the debugger stopped and did not stop.

  <project name="test" basedir="." default="build">
+   <target name="build">
-     <echo
-       message="Hello"
-       level="info"
+     />        
+     <echo>
-       Hello
-     </echo>
-   </target>
  </project>


- A '+' at the start of the line indicates that the debugger stopped at the 
  breakpoint.

- A '-' at the start of the line indicates that the debugger did not stop at
  breakpoint.


Consider this portion:

-     <echo
-       message="Hello"
-       level="info"
+     />        


It is unfortunate that the only breakpoint that works is on the closing tag,
"/>".  I would have hoped that a breakpoint on the opening tag, "<echo", would
also work.

Consider this portion:

+     <echo>
-       Hello
-     </echo>


In this case the reverse is true. You can set a breakpoint on the opening tag,
"<echo>", but not on the closing tag, "</echo>".

It would seem reasonable that if a breakpoint is set within an element that the
debugger stops before executing the task described by the element.

It is also worth noting that there is no visual clue that a breakpoint is valid
or not.  When attempting to place a breakpoint on an illegal line in the Java
editor the breakpoint is automatically moved down to the next legal line.
Comment 5 Denis Roy CLA 2009-08-30 02:18:28 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.
Comment 6 Michael Rennie CLA 2009-11-19 12:01:55 EST 
still valid
Comment 7 Lars Vogel CLA 2019-11-14 02:16:25 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.