Community
Participate
Working Groups
Please enhance the performance of the debugger step operations. Currently, if I step over or out, then Eclipse goes into stepping mode. If there is a lot of code to execute, this can take a long time with Eclipse hitting the CPU hard. If I step over a line, please set a hidden break point for the line after. If I step out of a method, please set a hidden break point for the line after the call. Only the current thread can hit the break point. When the break point is hit, remove it. With the above feature in place, Eclipse won't go into stepping mode. The step operation will happen very quickly since the thread will run until the next break point.
Can someone experiment on this?
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. -- The automated Eclipse Genie.
