| Re: [cdt-dev] breakpoints with basename |
|
As long as GDB is consistent in what it reports and what it expects for
these strange paths, the IDE should be able to handle the mapping
correctly. So to me it looks like the problem is with
MapEntrySourceContainer, which uses an IPath to store the original
path. I think the choice to use IPath was out of convenience, to allow
use of the parsing and comparison methods that it has, but the cost is
that the original path returned by GDB is lost. Cheers, Pawel Elena Laskavaia wrote: I know the reasons (kind of), that why I suggest to make it an option. The reason is when you compile on different host full path name would not match the path in debug info and debugger would fail to add breakpoint. This combined with some compiler weird source paths inserts creates unreadable full paths, like this: C:/builds/sources/bar/..\\foo\\main.c which nobody can parse (this is real example of path return by break-insert of 2.95 compiler + gdb 6.7). So what are the options in GDB-DSF? -----Original Message----- From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech Sent: February 22, 2008 2:22 PM To: CDT General developers list. Subject: Re: [cdt-dev] breakpoints with basename Elena Laskavaia wrote: |