#9167: cygwin: importing sage.libs.ecl yields a "no such process" error
-------------------------------------------------------+--------------------
Reporter: was | Owner: tbd
Type: defect | Status:
needs_work
Priority: major | Milestone:
sage-5.3
Component: cygwin | Resolution:
Keywords: cygwin spkg ecl | Work issues:
configure regeneration history issue
Report Upstream: Reported upstream. No feedback yet. | Reviewers:
Authors: Jean-Pierre Flori | Merged in:
Dependencies: #13324 | Stopgaps:
-------------------------------------------------------+--------------------
Comment (by dimpase):
Replying to [comment:56 dimpase]:
> well, I have finished the previous build, but then Sage was refusing to
start, throwing the usual fork() problems, even after repeated rebasealls
and reboots. I've decided to update Cygwin and uninstall as much as
possible of unneeded parts of Cygwin, in hope that it will help. But I am
not optimistic.
no, still no luck. I start to suspect that 2GB of RAM are not enough on
32-bit Windows 7 to run Sage. When I examine the location of Sage dlls
which produce these fork() failures, I see that
their preferred base addresses (set up by rebaseall) have nothing to do
with the actual places they are allocated;
these actual places may be already used by Win32 system dlls.
It could also be that it's just the 32-bit system is to blame, not the
relatively low by modern standards amount of RAM. It's pathetic that on
Linux 0.5GB of RAM are enough to have a well-running Sage, while here 2GB
are not enough.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9167#comment:59>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
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-trac?hl=en.
