Bug 559324

Summary: debugging in junit can't attach to source code editor
Product: [Eclipse Project] Platform Reporter: hui Deng <deng.hui>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: NEW --- QA Contact:
Severity: critical    
Priority: P3 CC: sarika.sinha, sueh
Version: 4.15   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard:
Attachments:
Description Flags
screenshot of bug none

Description hui Deng CLA 2020-01-19 10:14:29 EST
Created attachment 281546 [details]
screenshot of bug

When debugging in junit test, sometimes source code editor is not attached to debugger. 
I added 2 screenshots in attached file: "debugging GUI when bug occured" shows the problem that the cursor is not located on the source code line, as indicated by stack information. the next picture "debugging GUI after eclipse reboot.png" shown the normal state.

I meet this problem from eclipse 2019-03 to 2019-12.

please don't reply this message since I used obsolete account(the email address is from my previous employer) to report this bug.
why not register new account? it's difficult from China now!
Comment 1 hui Deng CLA 2020-01-19 10:19:55 EST
the problem easy occur after edit in debug mode
Comment 2 Sarika Sinha CLA 2020-01-20 23:59:47 EST
Can you please provide exact steps to reproduce the problem?
If you can attach a project it will help.
Comment 3 hui Deng CLA 2020-01-30 10:10:14 EST
The problem occurs occasionally, I don't know how to exact reproduce it step by step.
Comment 4 Sue H CLA 2020-07-20 20:07:58 EDT
I'm can't attach junit source code.  Is this related to this bug?
Comment 5 Sarika Sinha CLA 2020-07-21 08:05:27 EDT
(In reply to Sue H from comment #4)
> I'm can't attach junit source code.  Is this related to this bug?

Can you describe your problem and steps to reproduce?
Comment 6 Sue H CLA 2020-07-21 16:12:34 EDT
(In reply to Sarika Sinha from comment #5)
> (In reply to Sue H from comment #4)
> > I'm can't attach junit source code.  Is this related to this bug?
> 
> Can you describe your problem and steps to reproduce?

It turns out that there isn't a problem, and I was able to figure out what I was doing wrong.  So it has no bearing on this bug.  Sorry about that.