<div dir="ltr">I've been able to reliably reproduce this -- at least on my machine. This error seems to occur following a parse that was aborted due to running out of edges. ie:<div><br></div><div><div>"Probable runaway rule: parse/generate aborted (see documentation for *maximum-number-of-edges*)"</div> </div><div><br></div><div style>Once this has occurred it seems that anything that then involves unification results in the nested unification error, such as parsing, or loading a grammar.</div><div style><br></div><div style> I've attached a grammar that will give the max edges error if you try to parse "der man leyen-t dos bukh". Then you can reload the grammar or try to parse the string again to get the nested unification error.</div> <div style><br></div><div style>Ned</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 10, 2013 at 6:04 AM, Ann Copestake <span dir="ltr"><<a href="mailto:Ann.Copestake@cl.cam.ac.uk" target="_blank">Ann.Copestake@cl.cam.ac.uk</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> in case it helps - I recollect that error message as turning up in highly<br> misleading contexts. The ones I remember were code bugs - feature structure<br> creation not being called correctly. These could potentially turn up in<br> lkb/user-fns.lsp as well as in the main code, so if that's been modified, I'd<br> be suspicious.<br> <br> Best,<br> <br> Ann<br> <br> <br> <br> <br> </blockquote></div><br><br clear="all"><div><br></div>-- <br><a href="http://nedned.net" target="_blank">nedned.net</a> </div>