Bug 26268 - Entering a breakpoint at method declaration does not kick off debugger
Summary: Entering a breakpoint at method declaration does not kick off debugger
Status: VERIFIED DUPLICATE of bug 1591
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0.2   Edit
Hardware: PC Windows 2000
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 36513 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-11-14 06:55 EST by Alex Blewitt CLA
Modified: 2003-06-18 13:40 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 2002-11-14 06:55:57 EST
When I double click in the breakpoints bar against the side of a method 
declaration, and run in the debugger, the breakpoint doesn't fire. 

If I put a breakpoint by the first statement in the method, it does fire:

o  public static void main(String args[]) {
     System.out.println("No debugger");
   }

   public static void main(String args[]) {
o    System.out.prointln("Debugger fired");
   }

Can this be changed so that double-clicking against the method definition 
either fires the debugger, or moves the debug breakpoint to tne next available 
method?
Comment 1 Darin Wright CLA 2002-11-14 08:52:02 EST
There are several bugs in this area. Not committed to fix for 2.1 - marking as 
later.
Comment 2 Alex Blewitt CLA 2003-02-25 20:37:38 EST
This also happens when the breakpoint is at a commented out line as well.
I put in a breakpoint at a line with a statement (which fired the debugger)
and then wanted to comment out something for testing purposes. I later
discovered that the line I had commented was the one with the breakpoint in,
with the result that the debugger never fired that breakpoint.
Comment 3 Darin Wright CLA 2003-04-15 13:17:28 EDT
*** Bug 36513 has been marked as a duplicate of this bug. ***
Comment 4 Darin Wright CLA 2003-05-14 11:24:11 EDT
Marking as dup.
Comment 5 Darin Wright CLA 2003-05-14 11:24:26 EDT

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