Bug 392285 - Two projects having same file names, break point in one file is accessed by the other file
Summary: Two projects having same file names, break point in one file is accessed by t...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: Next   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-18 02:09 EDT by Reddy 2010eet2560 CLA
Modified: 2020-09-04 15:26 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reddy 2010eet2560 CLA 2012-10-18 02:09:47 EDT
I have two different projects(proj1 and proj2) in the work space with same file name(eg. foo.c). The contents of the file foo.c is different in the projects. I have the proj1/foo.c open and a break point is set in it. When I close the proj1/foo.c and open the proj2/foo.c and debug the proj2, it is stopping at the line no. at which proj1/foo.c has a breakpoint. And in the same way break point set in the proj2/foo.c applies to the proj1/foo.c
Comment 1 Marc Khouzam CLA 2012-10-19 13:51:58 EDT
Breakpoints are set using absolute path so this should not happen.

I cannot reproduce the problem.

Are you using the CDI debugger or the DSF one?
Comment 2 Reddy 2010eet2560 CLA 2012-11-07 22:21:07 EST
(In reply to comment #1)
> Breakpoints are set using absolute path so this should not happen.
> 
> I cannot reproduce the problem.
> 
> Are you using the CDI debugger or the DSF one?

I am using the DSF Debugger. I am still facing the problem. 

If I set a break point in one project it is being reflected in the other project which has same file name, 
when I run the project the breakpoint is hit, but breakpoint is not visible in UI. 

I did not close one project and opened the other one . Both the projects are there in the workspace.
Comment 3 Robert Hartmann CLA 2012-11-13 13:39:47 EST
Hi there,

Just a guess: Check in Debug-Configurations, which is the application to debug.

I remember, that I had a same problem while debugging or run a java-application.
The solution was to enter the correct application in ru-configuration or debug-configuration.

Best regards,
Robert