[cdt-debug-dev] Attempt to open file w/absolute path

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

> We are considering major changes in the source lookup related code that 
> includes the solution for this problem. I don't think it makes sense to 
> apply this patch now.
> 
> Mikhail Khodjaiants

Cool!

This is something that I'm very interested in. Will you be posting
something for comments?

Here are a couple of things I believe that a new design must take into
account if it is to survive a couple of generations:

- Let GDB do the source lookup if you can. It is often the same host OS
  as the toolchain and knows where and how to find the source files.

- Projectless debugging and development. Large existing projects will
  not be changed to be CDT projects. There is no large coordinated
  effort that I've heard about for this, but path handling is a very
  important piece to the puzzle.

- Host toolchain OS != Eclipse OS. I believe this is mostly a 
  Windows issue. Hmm.... strike that. Teams could be mixed
  Windows/Linux and binaries could migrate back and forth.
 
  Example: MingGW or CygWin toolchain and Windows hosted Eclipse

- There is no canonical representation. If a path originates
  from GDB, is used in Eclipse and fed back to GDB, then the
  path must *not* be converted to Eclipse speak and back to GDB 
  speak, because any such transformation is inheritely lossy.
  Eclipse must store the original Eclipse/GDB path.
  
  E.g. today breakpoints are not persisted correctly between
  debug sessions due to such lossy conversion.
  
  


-- 
Øyvind Harboe
http://www.zylin.com