Hi! On 19 Sep., 11:38, William Stein <[email protected]> wrote: [...] > Maybe you should try asking on the GAP list what those error messages mean?
I already found that the "recursion depth trap" is GAP's way of avoiding infinite recursion. They give the example gap> dive:= function(depth) if depth>1 then dive(depth-1); fi; return; end; function( depth ) ... end gap> dive(100); gap> OnBreak:= function() Where(1); end; # shorter traceback function( ) ... end gap> dive(6000); recursion depth trap (5000) But this would not explain why one and the same command triggers recursion depth (5000) the first time, recursion depth (0) the second time, and no error the third time. Anyway, currently I can not put my fingers on a reasonably short sequence of commands that trigger the error. And I would like to avoid a bug report of the type "HELP! Something goes wrong"... This is why I'd prefer an executable log file. Even if it where 10,000 lines long, it would be something that I could send to the GAP list. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
