Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Moving the RSE "Remote CDT Launch" feature into CDT

Hi,

With Galileo, the CDT will include DSF-GDB as an alternative to its
current debugging framework (CDI.)
DSF-GDB already has a Remote Launch which may be of interest to you.
Maybe it could even be sufficient for you, with some modifications?

Your Remote Launch which is based on CDI could also be added as
alternative Remote Launch (like all the other launches have
alternative for the CDT in Galileo), although we are gradually moving away
from CDI towards DSF-GDB.

I wonder about the RSE features though.  Do you see the dependence on RSE as
optional, or would it become mandatory if your Remote Launch would be included
in the CDT?

Thanks

Marc


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx on behalf of Oberhuber, Martin
Sent: Wed 3/4/2009 12:54 PM
To: CDT General developers list.
Cc: Target Management developer discussions
Subject: [cdt-dev] Moving the RSE "Remote CDT Launch" feature into CDT
 
Hi all,
 
As some of you may know, one part of the TM / RSE offering is a "Remote
CDT" Launch configuration, which allows 

*	Uploading files through RSE-provided Services
*	Launching the program remotely through an RSE-provided shell
*	Debugging remotely through a remote gdbserver instance (requires
local cross-gdb).

The implementation of this feature requires using CDT internal non-API
[1] <https://bugs.eclipse.org/bugs/show_bug.cgi?id=257402>  in order to
get the debugger configuration page into the launch config UI, which is
forbidden in Galileo.
 
We'd therefore think it makes sense to move the feature into the CDT [2]
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=267065>  -- on the RSE
side, only public API is being used. In other words, we propose adding a
new optional CDT feature "Remote Launch" which depends on the RSE, and
removing that feature from the RSE offering.
 
The feature itself doesn't expose any API (everything is "internal"), so
renaming the plugin and/or the package should not be an issue if that is
desired.
 
Does the CDT Community agree that this is a good thing to do?
Who is the right person to get in touch with for making it happen?
Is it realistic to get that done for M6?
 
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=257402
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=267065
 
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 

<<winmail.dat>>


Back to the top