Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] java.lang.AssertionError in GdbCliConsoleManager.stopConsole(

Hi Liviu,

I don't think this is a known problem. Does this happen with Stock
CDT, or with the Arm plug-ins installed too? I assume the latter for
the rest of this email.

IIRC the arm plug-ins create additional consoles for a launch? Are any
of them Debugger Consoles (i.e in the new debugger console view
instead of the traditional Eclipse console view)? If so, the code in
GdbCliConsoleManager is assuming that the console is a more narrow
type than it is. If so, then I think the assertion is wrong and should
simply be removed (there is an instanceof check on the next line).

However, I see a potential other problem. If you create your own
Debugger Console, do you also have the standard one in place too? If
so, then the manager's getConsole() should be getConsoles() and all of
the consoles associated with the launch should be terminated.


Jonah Graham
Kichwa Coders Ltd.

On 1 June 2017 at 13:04, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
> After upgrading everything to Neon.3, I continuously get an assertion error in the development Eclipse debug console:
> !ENTRY org.eclipse.debug.core 4 120 2017-06-01 14:59:03.744
> !MESSAGE An exception occurred during launch change notification.
> !STACK 0
> java.lang.AssertionError
>         at org.eclipse.cdt.dsf.gdb.internal.ui.console.GdbCliConsoleManager.stopConsole(
>         at org.eclipse.cdt.dsf.gdb.internal.ui.console.GdbCliConsoleManager.launchesTerminated(
>         at org.eclipse.debug.internal.core.LaunchManager$
>         at
>         at org.eclipse.debug.internal.core.LaunchManager$LaunchesNotifier.notify(
>         at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(
>         at org.eclipse.debug.core.Launch.fireTerminate(
>         at org.eclipse.cdt.dsf.debug.model.DsfLaunch.access$1(
>         at org.eclipse.cdt.dsf.debug.model.DsfLaunch$
>         at org.eclipse.debug.core.DebugPlugin$
>         at
>         at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(
>         at org.eclipse.debug.core.DebugPlugin$
>         at
> I cannot tell if this is harmful in any way, apparently not.
> Is this a known problem?
> Regards,
> Liviu
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top