On Sat, Sep 29, 2018 at 9:19 AM Simon King <simon.k...@uni-jena.de> wrote: > > Hi Dima, > > On 2018-09-29, Dima Pasechnik <dimp...@gmail.com> wrote: > > set_gap_memory_pool_size() > > controls the amount of memory GAP and libGAP get if started from Sage. > > The latter is dynamic, as opposed to "sage --gap" > > Do I understand correctly: libgap has dynamic pool size, but > gap-via-pexpect has not?
both use the same controls involving t_gap_memory_pool_size - why it's slightly different I don't know, perhaps one can find out by reading code... > That would explain why libgap can do what > gap-via-pexpect can't. But why does my computation work in "sage -gap", > but not in gap-via-pexpect? > > Anyway, using set_gap_memory_pool_size(2*get_gap_memory_pool_size()) > till everything works sounds like a reasonable way out. > > Thanks and best regards, > Simon > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
