I think this is classic multi-file problem. I think you have to do
both: set "Use
full file path to set breakpoints" and set Absolute File Path as
source lookup. Why you trying to add Project into source lookup path?
Tim Black wrote:
I had multiple main.cpp files in
the project, and regardless of which launcher/debugger I used, eclipse
always brought up the wrong file, one that appeared earlier
alphabetically in the project structure. I found a workaround here: http://www.eclipse.org/forums/index.php?t=msg&&th=75411&goto=235528#msg_235528.
It seems the only way to fix it
is if the ONLY entry in the Source Lookup Path in the Launch
Configuration is Absolute File Path. If I subsequently add the project
root to the
Source Lookup Path, either before or after Absolute File Path, the
problem returns.
I had thought that Source - "Search
for duplicate source files on the path" or Debugger - "Use full file path to set breakpoints" would
have corrected this lookup problem, but it didn't.
http://www.eclipse.org/forums/index.php?t=msg&&th=164595&goto=521270#msg_521270
Should these settings be responsible for correcting the problem of
resolving duplicate source file names in the debugger, instead of
having to change the Default Source Lookup Path to Absolute File Path?
What
does this Absolute
File Path entry mean?
Why would source file resolution only work when
it is the only item in the list?
I was leery of accepting anything
mentioning an "absolute file path" bc my team shares eclipse project
files and
launch configuration files. I don't
see any paths in the .launch files, so it
appears safe to share .launch files with this setting. Do you agree?
Thanks!
Tim
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
