Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331730

Summary: [debug] Breakpoint on the first statement of a base method with a callin binding attached broken
Product: [Tools] Objectteams Reporter: Jan Marc Hoffmann <exelnet>
Component: OTDTAssignee: Project Teams <objectteams.otdt-inbox>
Status: REOPENED --- QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann
Version: 0.7.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Jan Marc Hoffmann CLA 2010-12-02 17:22:27 EST 
If you add a breakpoint on the first statement of a base method with a callin attached to it, you will get tons of stops on the methodheader without any of them reaching your breakpoint.
Comment 1 Stephan Herrmann CLA 2010-12-03 17:40:06 EST 
The additional stops you are seeing could be intentional.
Please check the preference section at

  Preferences > Object Teasm > Debug > Visualization of callin dispatch

If you uncheck all three checkboxes stepping should no longer stop
at unexpected places, right?
Comment 2 Stephan Herrmann CLA 2011-01-26 18:53:33 EST 
I'm closing as invalid as I suspect what you were seeing is in fact
the intended behavior.
Feel free to reopen with more details if comment 1 didn't help.
Comment 3 Jan Marc Hoffmann CLA 2011-01-26 19:11:03 EST 
Uh I nearly forgot about this one. I just disabled all the options you mentioned. Same odd behaviour. The debugger stops at the method header several times.
Comment 4 Stephan Herrmann CLA 2011-01-28 18:11:31 EST 
Sorry, running out of time for M5.