I was shown the following way of getting a segmentation fault in Sage.
sage: var("q A")
sage: p = A*(1+1/A)-A-1
sage: (q^p).full_simplify()
This consistently causes a crash. The person who found it was doing some
actual work, got a crash, and boiled it down to a minimal example.
Daniel Bump
--
I tried importing functions from Singular's primdec_lib to use them in
comparison with sage's minimal_associated_primes(), but get a segfault
every time I use them after I use minimal_associated_primes() from Sage.
Can anyone explain why?
Example:
min_ass1=sage.libs.singular.function_factory.
There have been several tickets on segmentation faults concerning the
singular interface. Since they are all closed, I think this must be an
unknown case:
sage: R. = Integers(7)[]
sage: p = x**2-1
sage: p.factor()
Trying the same with GF works fine:
sage: R. = GF(7)[]
sage: p = x**2-1
sage: p
I'm sorry, I forgot to mention this step:
load_session('leaf_chamber_eqs_PM.sobj')
(as opposed to a = load('leaf_chamber_eqs_PM.sobj')
My apologies!
Cheers
Stan
On Thursday, September 8, 2016 at 3:53:57 PM UTC+2, vdelecroix wrote:
>
> The download link is
>
>
> https://cloud.sagemath.com/34b4b6
By the way, the problem persists no matter whether the .sobj file was
created using sage 6.8 or 7.3.
On Thursday, September 8, 2016 at 4:35:13 PM UTC+2, Stan wrote:
>
> Thanks for correcting the link. The .sobj file was generated by
> save_session(), and contains several dictionaries, variable
Thanks for correcting the link. The .sobj file was generated by
save_session(), and contains several dictionaries, variable definitions
etc. I did actually recreate it in sage 7.3 as I thought it might have been
a compatibility issue with sage 6.8, so if it is corrupt, there is some
problem tha
The download link is
https://cloud.sagemath.com/34b4b62a-2621-47c8-9bda-cde3a855f995/raw/leaf_chamber_eqs_PM.sobj
(the link by the OP is a HTML page that displays the content of the file)
There seems to be a problem with the content of your
leaf_chamber_eqs_PM.sobj file. Namely the dictionary
Dear all,
I am on debian jessy 64bit and after installing sage 7.3 I keep getting
segfault for the same worksheets that run smoothly in sage 6.8. I have now
managed to isolate a small example, which I uploaded to cloud.sagemath,
where it does not give a segfault message, but just runs forever.
Dr. David Kirkby wrote:
I'm just running the test suite of Sage 4.3.0.1 on 't2'. This was not
compiled on 't2', but on an old SPARC of mine. It is failing at this test.
Has anyone got a build on 't2' they have created on 't2', and can
confirm whether or not it passes or fails.
sage -t "deve
I'm just running the test suite of Sage 4.3.0.1 on 't2'. This was not compiled
on 't2', but on an old SPARC of mine. It is failing at this test.
Has anyone got a build on 't2' they have created on 't2', and can confirm
whether or not it passes or fails.
sage -t "devel/sage-main/build/sage/lf
Any time writing in pure python causes a segfault is a serious bug.
Glancing briefly at the code, I have a few ideas for what might have caused
it: I'll take a more detailed look in an hour or two.
Regardless of what's causing the crash, I'd suggest you use the methods
described at http://www.sag
I will explain how to make sage have a segmentation fault
with the following alarming message:
Unhandled SIGSEGV: A segmentation fault occured in SAGE.
This probably occured because a *compiled* component
of SAGE has a bug in it (typica
In 4.0.alpha0, this causes a segmentation fault:
--
| Sage Version 4.0.alpha0, Release Date: 2009-05-15 |
| Type notebook() for the GUI, and license() for information.|
---
13 matches
Mail list logo
