Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 259844 - [Debug] Breakpoints skipped on line number > 64k
Summary: [Debug] Breakpoints skipped on line number > 64k
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 547731 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-31 21:04 EST by Alain Picard CLA
Modified: 2019-05-30 10:42 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Picard CLA 2008-12-31 21:04:50 EST 
Build ID: I20080617-2000 

Steps To Reproduce:
1. Find a large .java file
2. Set a breakpoint at a line > 65536
3. Run program


More information:
You will notice that even if your code runs, that your breakpoint will never be triggered.

Another issue (java related I believe) is that an exception found in this area is reporting the wrong line number. I have one reporting line number 272 instead of 65808.
Comment 1 Darin Wright CLA 2009-01-05 14:31:18 EST 
This is a Java limitation. Line number debug attributes in class files are 16 bit unsigned integers - resulting in a max line number of 65535.
Comment 2 Andrey Loskutov CLA 2019-05-30 10:42:40 EDT 
*** Bug 547731 has been marked as a duplicate of this bug. ***