Enhancing Julia Debugging: Entry Points

Debugging in Julia can be significantly enhanced, particularly in dealing with large codebases, through the introduction of entry points.

When debugging extensive Julia code, the compiled mode proves to be practically useful due to its speed and freedom from conflicts with libraries. In contrast, the non-compiled mode easily becomes impractical due to its slow performance or potential library conflicts.

However, a notable drawback of the compiled mode is that it ignores breakpoints within sub-functions. Consequently, users are required to manually navigate through the code until the relevant subfunction is reached.

When repeatedly debugging functions at a deep level, the current approach involves placing breakpoints at all calling functions, necessitating multiple manual step-ins and step-outs to reach the desired section of code. This significantly disrupts the debugging flow and makes it challenging to maintain focus on the specific problem at hand.

Consider this idea: instead of manually stepping in and out at every level, why not let the Julia Debugger handle it automatically? If, instead of setting red breakpoints at all calling functions, users could designate orange entrance points, the debugger could identify these entry points and execute step-ins and step-outs automatically until the first red breakpoint is encountered.

Introducing this feature would greatly enhance the debugging experience, providing a more streamlined and focused approach to identifying and resolving issues in the code.

Note: If you can create a function that can find the entry points on its own, we’ll have a debugger that’s as good as those in other languages, but with the speed of Julia! This would make Julia even more appealing. However, I see this as a second step. First, I strongly suggest to improve the efficiency by manually setting the entry points. Right now, debugging in Julia becomes difficult as the project gets bigger.

The issue does not name files, tests, or a code entry point. Start by locating the debugger's compiled-mode breakpoint handling, then define how manually designated entry points should trigger automatic stepping until a red breakpoint is reached. Done means the proposed entry-point workflow is specified and covered for the relevant debugging modes.