Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT and the marketplace


I think William Riley figured it out in our CDT call today.

Each console that is missing is representing a RuntimeProcess and that

RuntimeProcess is created using DebugPlugin.newProcess(...).

However if those processes are using the attribute 


CDT will understand them to represent the GDB RuntimeProcess itself

(, and will prevent them from creating a standard 

console (since the GDB process now uses a Debugger Console instead).

Looking in the GNU ARM plugins code, I found 5 occurrences of

IGdbDebugConstants.GDB_PROCESS_CREATION_VALUE, in methods 

such as addServerProcess() for example. This seems to confirm the theory above.

I think you should simply not set that attribute for any other process than

the GDB process itself.

I've noticed that in a method called addSemihostingProcess() that attribute

is _not_ used, and I therefore assume that the console for that process still

shows as expected.

Let us know if that works out.

Thanks William for your help!


From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Liviu Ionescu <ilg@xxxxxxxxxx>
Sent: January 7, 2017 13:13
To: CDT General developers list.
Subject: Re: [cdt-dev] CDT and the marketplace

> On 7 Jan 2017, at 18:55, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
> I guess the problem is in CDT 9.2, and somehow related to the change in console processing.

I took a look at the changes since 9.1 and I noticed the addition of a GdbCliConsoleManager which has an `addConsole()` method.

I could not identify who is calling this, but if it needs to be explicitly called by the application, old code will obviously not register additional consoles.



cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Mailing list: cdt-dev CDT General developers list. About cdt-dev

Back to the top