Java Debugger in Eclipse: Limitation on lines of code

Question

I am working on a Java application and there are certain classes which are more than 60K lines of code. One challenge we always face is navigating thru debugger when lines cross 60K during debugging. When 60K is crossed, the debugger stops showing the code and values. One way we overcome this is to move the impacted function above 60K lines and then put the debugger again, but this process is inconvenient at times.

Question:

Where is the limitation, is it eclipse or java or something else which doesn't allow debugger to function properly beyond 60K ?

This sounds like a massive violation of the single reponsibility principle (and probably a few others as well). — Thomas
– Thomas, Commented Mar 3, 2020 at 8:20

howlger · Accepted Answer · 2020-03-03 09:50:28Z

1

The limitation is given by the Java bytecode format:

In the line number table, the line number is stored as an unsigned two bytes quantity (u2), which results in a maximum line number of 65 535.

Apart from that, the effective limitation is given by the people who have to read the code. 60k LOC is far too much that it would be readable code.

edited Mar 3, 2020 at 9:50

answered Mar 3, 2020 at 8:51

howlger

35k11 gold badges73 silver badges112 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Java Debugger in Eclipse: Limitation on lines of code

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related