#4181: Mysterious error somewhat related to 16-Bit signed integers on Mac OS X
-------------------------+--------------------------------------------------
Reporter: GeorgSWeber | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: sage-3.1.3
Component: porting | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Old description:
> On both my Mac OS X 10.4 / Xcode 25 boxes, one Intel and one PPC, the
> following Sage code runs through fine (hit return twice):
>
> sage: for p in prime_range(32768, 100000):
> EllipticCurve(GF(p),[0,1,1,10,13])
>
> Please note that the length of the interval is almost 70000, so quite
> some primes are involved.
> But if the startpoint of the range is lower the 32768, then Sage crashes,
> e.g. for:
>
> sage: for p in prime_range(31300, 32600):
> EllipticCurve(GF(p),[0,1,1,10,13])
>
> (note that the length of the interval is only 1300) one gets the
> following message with sage crashed:
>
> error: no more memory
> System 8672k:8672k Appl 8233k/438k Malloc 4030k/33k Valloc 4608k/404k
> Pages 1071/81 Regions 9:9
>
> halt 14
>
> The problem/bug can't be due to low physical RAM, or due to not enough
> virtual RAM for processes, since then the first line of code would have
> to crash, too. Which is not the case.
>
> It is not related to the mathematical code, since if the length of the
> interval of primes is only 100 or less, the code runs fine for
> startpoints above and (!) below 32768.
>
> The bug is triggered also if consecutively several small intervals (below
> 32768) are calculated, so it seems to be some caching / stack / heap /
> whatsoever related issue.
> It does not seem to occur on platforms other than Mac (OS X 10.4 only?),
> so I put this under the "porting" issues.
New description:
On both my Mac OS X 10.4 / Xcode 25 boxes, one Intel and one PPC, the
following Sage code runs through fine (hit return twice):
{{{
sage: for p in prime_range(32768, 100000):
EllipticCurve(GF(p),[0,1,1,10,13])
}}}
Please note that the length of the interval is almost 70000, so quite some
primes are involved.
But if the startpoint of the range is lower the 32768, then Sage crashes,
e.g. for:
{{{
sage: for p in prime_range(31300, 32600):
EllipticCurve(GF(p),[0,1,1,10,13])
}}}
(note that the length of the interval is only 1300) one gets the following
message with sage crashed:
{{{
error: no more memory
System 8672k:8672k Appl 8233k/438k Malloc 4030k/33k Valloc 4608k/404k
Pages 1071/81 Regions 9:9
halt 14
}}}
The problem/bug can't be due to low physical RAM, or due to not enough
virtual RAM for processes, since then the first line of code would have to
crash, too. Which is not the case.
It is not related to the mathematical code, since if the length of the
interval of primes is only 100 or less, the code runs fine for startpoints
above and (!) below 32768.
The bug is triggered also if consecutively several small intervals (below
32768) are calculated, so it seems to be some caching / stack / heap /
whatsoever related issue.
It does not seem to occur on platforms other than Mac (OS X 10.4 only?),
so I put this under the "porting" issues.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4181#comment:1>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
