Bug 27150 - Breakpoint not honoured
Summary: Breakpoint not honoured
Status: RESOLVED DUPLICATE of bug 1591
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-26 06:48 EST by Philipe Mulet CLA
Modified: 2003-05-14 11:30 EDT (History)
0 users

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 Philipe Mulet CLA 2002-11-26 06:48:06 EST 
Build 2.1-M3

On code like, where a breakpoint is located on first statement which is empty 
variable declarations, the debugger will not stop (jdk1.4.1):

	public FlowInfo analyseCode(
		BlockScope currentScope,
		FlowContext flowContext,
		FlowInfo flowInfo) {

(*)		FlowInfo thenFlowInfo, elseFlowInfo;

		// process the condition
		flowInfo = condition.analyseCode(...)
Comment 1 Darin Wright CLA 2002-11-26 09:47:43 EST 
We are incorrectly allowing the user to put a breakpoint on a non-executable 
line. We have experimented with using the JDOM to verify breakpoint locations, 
but this has turned out to be slow in large compilation units.

Marking as later (there are many breakpoint location bugs currently on hold).
Comment 2 Darin Wright CLA 2003-05-14 11:30:17 EDT 
marking as dup.
Comment 3 Darin Wright CLA 2003-05-14 11:30:38 EDT 

*** This bug has been marked as a duplicate of 1591 ***