Hi Justin! On 24 Sep., 19:38, "Justin C. Walker" <[email protected]> wrote: > That is the crux of the problem. This is a race condition (multiple > outcomes, depending on the ordering of operations, many of which are > outside of your control. Debugging of these problems is why we pay > software developers the big bucks :-}
But, as stated in my previous posts, there is an alternative potential source of problems: The Gap and the Singular interfaces use the *same* file for processing long command lines; and moreover, Gap instances that occur in different branches of a parallelised method share the same file as well. Since I make heavy use of both Gap and Singular and use parallelisation in my tests, there is no need of a race condition for explaining the problems that I met. One could solve part of the problem by making the filename dependent on the pid of the interface instance. However, if one tries to cache the filename, then Gap instances in different branches of a parallelised method share the cache although they have different pid, provided that the cache was created in the main Sage loop. Cheers, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
