Re: [cdt-dev] Upcoming release dates (was CDT8.4 + 8.5 - all debug butto

[Liviu Ionescu <ilg@xxxxxxxxxx>]

On 03 Dec 2014, at 22:27, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:

>> then how do you explain the same problems occurring without my plug-ins?
> 
> Maybe it is not your plugins at all.  It could be CDT plugins but that
> the exception is triggered in your environment.

I never exclude the possibility that my code has bugs. the GNU ARM Eclipse is a suite of 19 plug-ins, most with dependencies, so I cannot simply test them one by one, but I'll try to identify the one that is causing the exceptions.

>> because Derek clearly reported them. one of his other plug-ins having the same
>> StackOverflow problem?
> 
> Maybe the stack overflow happens because there are too many buttons or something?

I have only one additional button, a Reset button, used to reset the debugged target:

  <extension
        point="org.eclipse.ui.menus">
     <menuContribution
           locationURI="toolbar:org.eclipse.debug.ui.main.toolbar?after=additions">
        <command
           commandId="org.eclipse.debug.ui.commands.Restart"
           icon="icons/elcl16/restart_co.gif"
           disabledIcon="icons/dlcl16/restart_co.gif"
           label="%restartButton.label"
           style="push"
           tooltip="%restartButton.tooltip">
        </command>
     </menuContribution>
  </extension>

I doubt this is the problem.

> My guess is that most committers have pretty basic setups.
> If you want to describe your setup, we could try to run the same thing and
> reproduce the StackOverflow problem.

my setup includes the GNU ARM Eclipse plug-ins:

http://gnuarmeclipse.livius.net/blog/

you don't even need to install all of them; the build, the cortex-m template and the j-link features are enough, once you install them the stack overflow occurs.

> I forgot if we have a bug opened for this?  If not, I suggest you create one
> and poste info about your setup.

the Stack Overflow bug is reported, documented and confirmed from another user:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=440033

but I still would not rule out that that the debugger behaviour is a distinct problem.

> It is still possible the problem is in CDT itself, but I don't know where to look
> for it.  I'll do a git diff between Kepler and Luna like you suggest just in case.
> Can you confirm which version of CDT you are using in each case?

I would say that 8.3.0 was the last functional version.

thank you,

Liviu