Bug 491289 - Breakpoints from one project is hit in another project for Scrapbook page
Summary: Breakpoints from one project is hit in another project for Scrapbook page
Status: REOPENED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 508223 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-07 19:06 EDT by Sarika Sinha CLA
Modified: 2024-05-06 18:48 EDT (History)
4 users (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 Sarika Sinha CLA 2016-04-07 19:06:56 EDT 
Taking the bug out from Comment#63 of Bug 5188

A snippet in project P2 that uses a type and a method that are also in P1, and the method in P1 contains a breakpoint. Executing that snippet hits the breakpoint.
Comment 1 Sarika Sinha CLA 2016-08-29 02:18:07 EDT 
Adding to this, 
I just faced an issue that with a simple Scrapbook page with syout statement works fine on an empty workspace. After I debug any program in this workspace with breakpoints (not with same type or method). It stops at ScrapbookMain1.eval at line Number 28.

So I tried this out and I can reproduce this in Luna, Mars, Neon as well. S nothing new .

Here I am not debugging Scrapbook but scrapbook execution is like an evaluation.
Comment 2 Sarika Sinha CLA 2016-11-28 00:54:05 EST 
*** Bug 508223 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Genie CLA 2020-05-19 03:45:34 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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 4 Sarika Sinha CLA 2020-05-19 07:01:36 EDT 
Not resolved yet.
Comment 5 Eclipse Genie CLA 2022-05-14 15:22:43 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.
Comment 6 Eclipse Genie CLA 2024-05-06 18:48:51 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.