Over a million developers have joined DZone.

Better Debugging with Eclipse: Step Into Selection

DZone's Guide to

Better Debugging with Eclipse: Step Into Selection

Learn how to use the complicated "step into selection" feature of Eclipse while debugging.

· Agile Zone
Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. Brought to you in partnership with CA Technologies

Some might say that Eclipse is too powerful and has too many features. But to me, the many small and somehow hidden gems can make a big difference in my daily life. One of these features is ‘Step Into Selection’ while debugging.

Very often I have a source line with nested function calls like this:

Image title

I would like to step into the outer function FAT1_CheckCardPresence(), but when I do a ‘step-into’, it will first step into the CLS1_GetStdio() function. So there I have to do a ‘step-out’, and if there are multiple inner (nested) function calls, this requires many ‘step-into’ and ‘step-out’ clicks and operations.

There is a feature to avoid that: Step Into Selection :-)

I can select or click into the name and use the context menu ‘Step Into Selection’:

Image title

Instead of the context menu, I can use the Run menu too:

Image title

Or an even better way: I have use CTRL+ALT and click with the mouse (hyperlink mode):

Image title


For nested function calls, I do not need to step-into all the nested functions: I can use ‘Step Into Selection’ feature instead. This saves me many steps and clicks every day :-).

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies

eclipse ,java ,agile

Published at DZone with permission of Erich Styger, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}