Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367601 - [breakpoints] Run to line/breakpoint do not consider end-of-block as valid location
Summary: [breakpoints] Run to line/breakpoint do not consider end-of-block as valid lo...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-28 10:22 EST by Blessed Geek CLA
Modified: 2020-03-24 09:37 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blessed Geek CLA 2011-12-28 10:22:11 EST
Build Identifier: M20110909-1335

Debugger does not consider end-of-block brace bracket line as valid locations.

The effect is, I am unable to run debugger to end of a for loop without pacing thro thousands/gazillions of iterations to find out the consequences on the variables of the loop.

Reproducible: Always

Steps to Reproduce:
1. Put a break point at java.util.Collections, at line 158
2. Try run to line 164. Debugger responds with line not a valid location.
3. Try run to line 165. Debugger responds with line not a valid location.
4. Try to place a breakpoint at line 164 or 165. Debugger does not consider them as valid locations.

[code]
157 public static <T> void sort(List<T> list, Comparator<? super T> c) {
158 Object[] a = list.toArray();
159 Arrays.sort(a, (Comparator)c);
160 ListIterator i = list.listIterator();
161 for (int j=0; j<a.length; j++) {
162    i.next();
163    i.set(a[j]);
164 }
165 }
[/code]
Comment 1 Blessed Geek CLA 2011-12-29 14:16:02 EST
Conditional breakpoint j==a.length-1 did not work.
Comment 2 Eclipse Genie CLA 2020-03-24 09:37:40 EDT
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.