Bug 560253 - After export and import of breakpoints, trigger point doesnt work.
Summary: After export and import of breakpoints, trigger point doesnt work.
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.15   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-17 23:34 EST by Vikas Chandra CLA
Modified: 2024-01-29 13:33 EST (History)
0 users

See Also:

Attachments
breakpoint used (39.67 KB, application/octet-stream)
2020-02-17 23:34 EST, Vikas Chandra CLA 		no flags Details
add this patch (1.03 KB, application/octet-stream)
2020-02-17 23:37 EST, Vikas Chandra CLA 		no flags Details
View All 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 Vikas Chandra CLA 2020-02-17 23:34:31 EST 
Created attachment 281843 [details]
breakpoint used

I used the following breakpoint export
Comment 1 Vikas Chandra CLA 2020-02-17 23:37:14 EST 
Created attachment 281844 [details]
add this patch

And try to debug

package pack;

public record r() . {

}


Do a clean ->build all 

The trigger breakpoint should be used in resumeOnSyntaxError (Parser.java)
Comment 2 Eclipse Genie CLA 2022-02-07 11:16:38 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 2024-01-29 13:33:39 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.