| RE: [cdt-patch] Another try at Cygwin GDB - mi.core |
Thanks, Dave, sounds like a much cleaner approach. I'll give it a try.
Doug Schaefer
Senior Staff Software Engineer
Rational - the software development company
Ottawa (Kanata), Ontario, Canada
-----Original Message-----
From: David Inglis [mailto:dinglis@xxxxxxx]
Sent: Tuesday, November 26, 2002 12:20 PM
To: cdt-patch@xxxxxxxxxxx
Subject: Re: [cdt-patch] Another try at Cygwin GDB - mi.core
You could actually do the same thing without making changes to MISession
or the SourceManager. What you would do, is in the CygwinGdbDebugger create your
own mi CommandFactory which extends the default, but overrides the
createMIEnvironmentDirectory(dirs) method which then translate the dirs to cygwin dirs,
then set the CommandFactroy on the MISession (setCommandFactory()). This is all local
to the create methods of ICDebugger for CygwinGDBDebugger. I hope this is clear....
Schaefer, Doug wrote:
> I have made another attempt at supporting Cygwin GDB without messing
> with native GDB. This patch (and the following one for mi.ui) creates a
> new debugger for Cygwin GDB. It subclasses the GDBDebugger but sets a
> flag in MISession to not that this is Cygwin. The Source Manager checks
> the flag and converts the path if necessary. Please review.
>
[snip]
_______________________________________________
cdt-patch mailing list
cdt-patch@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-patch