[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] GDB 6.5 does not work in eclipse
|
Well, when people create a simple managed build project, compile it and
try to debug it, they expect it to work without doing any additional
source mapping.
The new attribute "fullname" has been added recently to the file
attributes in addition to the "file" attribute, For example:
...
file="../main.c",fullname="/cygdrive/c/runtime-workspace3.2/cdt-test/mai
n.c" ....
This is very handy, because gdb knows the compilation path and we don't
have to use the source lookup to find files compiled with relative
paths. So, I changed the "MIFrame" class to check if the "fullname"
attribute is present to get the full path. But now I realize that the
drawback is this problem with the cygwin paths.
> The correct solution is to implement the "info shared" MI counterpart.
There is an MI command for it - "file-list-shared-libraries", but it is
not implemented in 6.5.
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx
[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Alain Magloire
Sent: 03 November 2006 17:52
To: CDT Debug developers list
Subject: RE: [cdt-debug-dev] GDB 6.5 does not work in eclipse
> 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.
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
