Dear Sage Support, I'd like to debug some ugly problem that I have with GAP (really mysterious: Compute some examples -> example #45 fails with a recursion depth trap -> repeat example #45 -> it works without problem -> compute more examples -> #110 fails -> repeat #110 -> it works).
I know how I can produce a log file for the communication between Sage and GAP. Problem: In some cases a command buffer (gap._local_tmpfile ()) is used to store the commands for GAP, since this is much faster for long commands. But it is bad for debugging, since the commands from the buffer can't be seen in the log file (and they aren't visible in GAP's error message either). Is there a way to (temporarily) switch off the use of the command buffer? Or (which would even be better) is there a way to let the log file document *all* commands to GAP, regardless whether they are buffered or not? Eventually, I'd like to have a log file that provides a sequence of commands that can be directly read into GAP, in order to have something that hopefully triggers the error and thus helps to locate it. Best regards, Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
