> On Oct 4, 2017, at 22:54 , Sébastien Labbé wrote:
>
> ... and today running the latest version 8.1.beta7 I get the same thing as
> for beta5:
I think the original report (on sage_release@) reported that there was a
segfault following the runtime error you show below. Did that happen for yo
... and today running the latest version 8.1.beta7 I get the same thing as
for beta5:
┌┐
│ SageMath version 8.1.beta7, Release Date: 2017-10-03 │
│ Type "notebook()" for the browser-based notebook interface.
Replacing sig_str() with sig_on() in matrix_integer_dense.pyx:_cinit
resolves it.
Probably sig_str() is broken in the new Cython.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, se
Same on OpenSuSE. Backtrace:
#2 0x7fffe67d4194 in flint_memory_error () at memory_manager.c:44
#3 0x7fffe67da428 in flint_malloc
(size=size@entry=18446744073709551608)
at memory_manager.c:58
#4 0x7fffe6860c86 in fmpz_mat_init (mat=mat@entry=0x7ffd9efe07c0,
rows=92233720368
Thanks for the reply. I had trouble getting those tracs to make it work,
but installed gcc 7.2 and made it past the error.
On Tuesday, October 3, 2017 at 3:55:45 PM UTC-5, John H Palmieri wrote:
>
> The problem with gcc has been reported here:
> https://trac.sagemath.org/ticket/23898. No one see
On Ubuntu 16.04, I get:
┌┐
│ SageMath version 8.1.beta5, Release Date: 2017-09-11 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.
Does the function:
get_memory_usage
Do what you want? If you want to know what objects are in memory then maybe
something like:
sage: *import* *gc*
sage: gc.get_objects()
Or other related gc commands might give what you want. Or you could use
https://pypi.python.org/pypi/memory_profiler by
> On Oct 3, 2017, at 23:53 , Vincent Delecroix <20100.delecr...@gmail.com>
> wrote:
>
> Dear all,
>
> I am not sure when it started to fail but I got the following on 8.1.beta7
>
> sage: Matrix(ZZ, sys.maxsize, sys.maxsize)
> *** Error in `python': free(): invalid next size (fast): 0x0
As far as I know, I am the first to report this error (and not the only
one to have built 8.1.beta7).
On 04/10/2017 18:38, David Roe wrote:
No, I mean that there is no segfault: the RuntimeError is raised
successfully.
David
On Wed, Oct 4, 2017 at 10:31 AM, Vincent Delecroix <
20100.delecr...@
No, I mean that there is no segfault: the RuntimeError is raised
successfully.
David
On Wed, Oct 4, 2017 at 10:31 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
> Do you mean that you report the same issue on 8.1.beta7? I am recompiling
> 8.1.beta6 right now to see.
>
> Vincent
>
>
> O
Do you mean that you report the same issue on 8.1.beta7? I am
recompiling 8.1.beta6 right now to see.
Vincent
On 04/10/2017 18:30, David Roe wrote:
It seems to be okay in 8.1.beta6.
David
On Wed, Oct 4, 2017 at 10:24 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
And the issue is
It seems to be okay in 8.1.beta6.
David
On Wed, Oct 4, 2017 at 10:24 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
> And the issue is still there after a fresh build from scratch!
>
>
> On 04/10/2017 08:53, Vincent Delecroix wrote:
>
>> Dear all,
>>
>> I am not sure when it started to
And the issue is still there after a fresh build from scratch!
On 04/10/2017 08:53, Vincent Delecroix wrote:
Dear all,
I am not sure when it started to fail but I got the following on 8.1.beta7
sage: Matrix(ZZ, sys.maxsize, sys.maxsize)
*** Error in `python': free(): invalid next size (fast):
Hi
Suppose I have a polynomial Ideal 'J' and I want to call J.groebner_basis()
. My goal is to profile the memory usage of groebner basis computation in
SageMath. How can I do this from the sage command line ?
Regards,
Rusydi
--
You received this message because you are subscribed to the Google
14 matches
Mail list logo
