RE: [cdt-debug-dev] GDB 6.5 does not work in eclipse

[Alain Magloire <alain@xxxxxxx>]

> From: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
> Sent: Friday, November 03, 2006 12:06 PM
> To: CDT Debug developers list
> Subject: RE: [cdt-debug-dev] GDB 6.5 does not work in eclipse
> 
> Alain,
> It's a known issue. gdb 6.4 returns the cygwin-style source paths. The
> earlier versions return windows-style source paths.


It was my impression if you compile with the full pathname, then you will
get windows style paths:

 cc -g -c C:\Workspace\Project\src\a.c

But if you do the compilation with relative path you will end up with cygwin
paths

  cc -g -c a.c

> The workaround is to
> add a common path mapping that maps "/cygwin/c/" to "C:/". Of course, it
> is not a solution.

Why? It seems like a valid solution to me and one of the reason we added the
path mapping code.  Did you something else in minde?

> There is also a problem with "info shared", which is now uses the same
> format as for Linux. It is easy to fix, but what to do with the earlier
> versions? Should we create a new debugger type for >= gdb 6.4?
>

That is trickier.  The more problem is that every time we use CLI commands
instead of MI we can get problems since there is no guaranty on the format.
The correct solution is to implement the "info shared" MI counterpart.