Bug 543488 - Using debug on interface methods
Summary: Using debug on interface methods
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.9   Edit
Hardware: PC Windows 7
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-16 03:48 EST by 均杰 朱 CLA
Modified: 2023-04-10 16:51 EDT (History)
1 user (show)

See Also:


Attachments
Inside is the Chinese explanation. (132.91 KB, image/png)
2019-01-16 03:48 EST, 均杰 朱 CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description 均杰 朱 CLA 2019-01-16 03:48:16 EST
Created attachment 277167 [details]
Inside is the Chinese explanation.

EN: When I add a breakpoint in the interface to the method and start debug, it will stay here. I did not call it. Only by canceling this breakpoint, debug will continue to run. If the breakpoint is not added to the method, debug will run normally.

I'm sorry I can't understand. This is an interpreter.

CN: 当我在 接口中加上断点  (bug)在方法上 ,  启动 debug 时, 他会停留在这里 , 我并没有调用 ,  只有把这个断点 取消掉  ,debug  才会接着往下运行,   若断点不加在方法上 , debug 能正常运行 
: 看不懂 我感到很抱歉,  这是翻译
Comment 1 Sarika Sinha CLA 2019-01-16 21:58:46 EST
Please state the exact problem and provide steps to reproduce the problem.
Comment 2 Eclipse Genie CLA 2021-01-06 19:31:16 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-04-10 16:51:12 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.