My analysis returns an analysed AST and reference resolution runs most of the time on nodes of this analysed AST. But at some nodes in the AST, reference resolution is called on the original node and the original AST. You can see it at revision 21202 of https://svn.strategoxt.org/repos/StrategoXT/tiger-spoofax. Everytime a node is resolved, the AST and the node are debugged. Everything works fine for most nodes but not for types in variable declarations. Here, the original AST is used.

Submitted by Guido Wachsmuth on 2 September 2010 at 00:27

It’s possible that there’s no node with that origin in the desugared AST. We should increase robustness in this case by looking at the surrounding nodes (StrategoTermPath.getTermPathWithOrigin()).

I checked the Error Log and it says: Could not determine term corresponding to Tid(“vector”) in resulting AST. The corresponding exception is raised by the method you mentioned.

This happens if origin information is missing.