I have a Sage package/module that does parallelism by forking and communicating over pipes. This of course forks the whole Sage executable.
This seems to sometimes (but rarely) result in any of a large number of problems: double-frees, corrupted internal glibc structures, hangs, null pointers in absurd places, and so on. Is this a known bug? Is this something that should work? Is forking Sage just impossible to support? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
