[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-debug-dev] Translating CygWin path names to WIndows paths and back again
|
I expect this issue to be handled in CDT 3.0, but if anyone has any
tricks up their sleeves that they could share, it would be much
appreciated.
It is necessary to translate to/from CygWin paths at the lowest possible
level in the GDB/CDT interface, such that "poisoned paths" (CygWin
paths) do not spread throughout Eclipse CDT.
Below is an example of where I've hacked CDT...
Index: MIBreakpoint.java
===================================================================
RCS file:
/home/tools/org.eclipse.cdt.debug.mi.core/mi/org/eclipse/cdt/debug/mi/core/output/MIBreakpoint.java,v
retrieving revision 1.5
diff -u -r1.5 MIBreakpoint.java
--- MIBreakpoint.java 17 Sep 2004 18:59:35 -0000 1.5
+++ MIBreakpoint.java 29 Nov 2004 17:36:37 -0000
@@ -11,6 +11,8 @@
package org.eclipse.cdt.debug.mi.core.output;
+import org.eclipse.cdt.utils.path.PathTranslator;
+
/**
* Contain info about the GDB/MI breakpoint info.
*<ul>
@@ -234,7 +236,7 @@
} else if (var.equals("func")) { //$NON-NLS-1$
func = str;
} else if (var.equals("file")) { //$NON-NLS-1$
- file = str;
+ file = PathTranslator.guessAbsolutePath(".", str);
} else if (var.equals("thread")) { //$NON-NLS-1$
threadId = str;
} else if (var.equals("line")) { //$NON-NLS-1$
--
Øyvind Harboe
http://www.zylin.com
