Community
Participate
Working Groups
Build Identifier: 20100917-0705 When editing a path maping using Preferences > C/C++ > Debug > Common Source Lookup Path, the compilation path will convert all forward slashes do backslashes. This prevents the user to enter the correct path for cygwin. I.E. if users need to enter new path mapping to a cygdrive (from C:\Documents to /cygdrive/c/Documents), they end up with backslashed path (\cygdrive\c\Documents). If the cygwin path contains some backslash-escaped spaces, they do not get converted and break the path. Reproducible: Always Steps to Reproduce: 1. Create a new Path Mapping 2. Enter POSIX-style cygwin path to compilation path 3. forward slashes get converted
CQ:WIND00DE688
(In reply to comment #1) > CQ:WIND00DE688 Martin, just out of curiosity, what does this cryptic message mean? :) I have seen you add them before but never had a chance to ask.
(In reply to comment #2) > > CQ:WIND00DE688 > Martin, just out of curiosity, what does this cryptic message mean? It is a cross-reference to our Wind River internal bug tracking system. Having that special pattern in a comment helps me make bugzilla queries to show current status of those bugzilla items that refer to an internal tracking item. Sometimes it takes years until a "cosmetic" issue in Eclipse or CDT is resolved. It also isn't important for us to contribute a patch ourselves. Thanks to the Xref, I can update (and close) internal tracking items related to bugzilla's that were fixed with a given release of Eclipse or the CDT when we adopt it. I also have cross references the other way round, so if somebody adds a comment (or finds a solution) internally, I can update bugzilla.
This bug has been fixed as part of the Source Lookup work in Bug 472765. It has been resolved by using Strings instead of Path type when storing and displaying compilation paths.
