Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] reusing CDT Standalone Debugger running instance

OK, I have added for this.

Some comments not related to the bug below:

On 2 July 2015 at 04:05, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> wrote:
Hi Jonah,

I'm not aware of any work that have been started in this area. It would be a great enhancement! I think looking at how "Open file" works is a good idea. About a separate script/executable not being desired, it's really a matter of taste and what your users need. As you are probably aware, the debugger can be launched from an existing Eclipse installation using the script under the stand-alone debugger plugin, in eclipse/plugins/org.eclipse.cdt.debug.application_*/scripts/
You can also install the script with the
For me one of the extra complications is that it needs to work multi-platform (At least Windows/Linux for now). But one step at a time.

We also packaged it as it's own download for the Mars release so that people who only need the debugger can benefit from a smaller download. It's also a slightly simpler way of launching the debugger in the sense that it's just a regular executable at the root of the installation instead of a script to be executed in a subdirectory.
I quite like what you did with this. I think it makes the entry easier for new users.
If you need to provide the command-line debugger as part of a larger, fully functional Eclipse, I can see there a valid use case of using a script along side the normal Eclipse executable. In fact, that's how it is with the Eclipse IDE for C/C++ Developers package.

"On my machine cdtdebug -e <elf> takes 10-11 seconds to start and get to breakpoint at main.
relaunching from within CDT takes < 1 second."

I just want to make sure that you know that you can relaunch from the stand-alone debugger from the UI just like in normal CDT :) About the 10-11 secs, I'd be curious to look at the plugin load times, perhaps there's some improvement there to be made on the CDT side. There's also probably a lot of time spent starting the Eclipse platform itself.
Yes, the relaunching within the already running standalone debugger is great, and I am pleased to see that those GUIs weren't stripped out when the new simplified GUIs were added. 

In any case, I think it would be great if you created a bug on Bugzilla for this enhancement of reusing the running instance so that people could help and follow your progress.
As above, Bug 471667


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Jonah Graham [jonah@xxxxxxxxxxxxxxxx]
Sent: Wednesday, July 01 2015 11:35 AM
To: CDT General developers list.
Subject: [cdt-dev] reusing CDT Standalone Debugger running instance

Hi devs,

I am interested in making it possible to reuse the running CDT Standalone Debugger so that subsequent debug sessions can be started without having to relaunch Eclipse fully. i.e. this is for debug something like works for opening files.

I am trying to save some time[1] in launching, plus avoid user error such as workspace in use. 

Has anyone started work in this area? I have previously seen comments that indicated a separate script/executable for the standalone debugger is not desired. 

[1] On my machine cdtdebug -e <elf> takes 10-11 seconds to start and get to breakpoint at main.
relaunching from within CDT takes < 1 second.
But I am comparing against other standalone debuggers like ddd or gdbtui which both start in < 1 second.
Additionally, I want to deploy the command line launching of the debugger into a larger eclipse installation which may have many many more bundles.


cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top