analysis of stratego editor fails with

org.spoofax.interpreter.core.InterpreterErrorExit: Internal error: with clause failed unexpectedly in rule ‘declare-globals’
1
at org.strategoxt.lang.InteropSDefT.evaluate(InteropSDefT.java:196)
at org.strategoxt.lang.InteropSDefT.evaluate(InteropSDefT.java:185)
at org.strategoxt.lang.InteropSDefT$StrategyBody.evaluate(InteropSDefT.java:247)
at org.spoofax.interpreter.core.Interpreter.invoke(Interpreter.java:69)
at org.strategoxt.HybridInterpreter.invoke(HybridInterpreter.java:356)
at org.strategoxt.imp.runtime.Environment$1.invoke(Environment.java:189)
at org.strategoxt.imp.runtime.services.StrategoObserver.invoke(StrategoObserver.java:550)
at org.strategoxt.imp.runtime.services.StrategoObserver.invokeSilent(StrategoObserver.java:589)
at org.strategoxt.imp.runtime.services.StrategoObserver.update(StrategoObserver.java:289)
at org.strategoxt.imp.runtime.services.StrategoObserverUpdateJob.analyze(StrategoObserverUpdateJob.java:29)
at org.strategoxt.imp.runtime.services.StrategoAnalysisQueue$UpdateJob.run(StrategoAnalysisQueue.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.strategoxt.lang.StrategoErrorExit: Internal error: with clause failed unexpectedly in rule ‘declare-globals’
1
at org.strategoxt.lang.compat.report_failure_compat_1_0.invoke(report_failure_compat_1_0.java:53)
at org.strategoxt.stratego_lib.report_with_failure_0_2.invoke(report_with_failure_0_2.java:34)
at trans.declare_globals_0_0.invoke(declare_globals_0_0.java:220)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:27)
at org.strategoxt.lang.SRTS_all.mapIgnoreAnnos(SRTS_all.java:86)
at org.strategoxt.lang.SRTS_all.mapMaintainAnnos(SRTS_all.java:127)
at org.strategoxt.lang.SRTS_all.map(SRTS_all.java:66)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:21)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:28)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.lang.SRTS_all.map(SRTS_all.java:60)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:21)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:28)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.lang.SRTS_all.map(SRTS_all.java:60)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:21)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.lang.SRTS_all.invoke(SRTS_all.java:28)
at org.strategoxt.stratego_lib.m_135.invoke(m_135.java:33)
at org.strategoxt.stratego_lib.alltd_1_0.invoke(alltd_1_0.java:25)
at trans.declare_globals_top_0_0.invoke(declare_globals_top_0_0.java:82)

Submitted on 1 December 2010 at 17:28

This indicates that there’s some unanticipated AST element in the Stratego code or the Stratego signatures. The Eclipse error log likely also shows a Stratego-level stack trace (as opposed to the Java trace above) with the offending AST element. Could you check if there is such a trace or any other additional information in the error log, possibly in the tiny “message” field of the error details dialog?

It seems this issue has been resolved in the latest “unstable” version, v0.5.3. See the FAQ for information on how to update to it.