Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331730 - [debug] Breakpoint on the first statement of a base method with a callin binding attached broken
Summary: [debug] Breakpoint on the first statement of a base method with a callin bind...
Status: REOPENED
Alias: None
Product: Objectteams
Classification: Tools
Component: OTDT (show other bugs)
Version: 0.7.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Teams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 17:22 EST by Jan Marc Hoffmann CLA
Modified: 2011-01-28 18:11 EST (History)
1 user (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 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.