[sage-devel] Re: Segmentation Fault

2023-05-30 Thread dmo...@deductivepress.ca
I opened issue #35696 for this, and put a diagnosis there. On Monday, May 29, 2023 at 10:00:05 PM UTC-6 dmo...@deductivepress.ca wrote: > I'm surprised that this hasn't been reported previously, because we can > get a crash even without atan or an

[sage-devel] Re: Segmentation Fault

2023-05-29 Thread dmo...@deductivepress.ca
I'm surprised that this hasn't been reported previously, because we can get a crash even without atan or any division: sin( x*(x+1) - x^2 - x ) # this crashes sage This also crashes with sinh or cos or tan in the place of sin, but not with exp or log. PS I verified on CoCalc that this is no

[sage-devel] Re: Segmentation Fault

2023-05-29 Thread Nils Bruin
Localized a bit further: var("q A") p = A*(1+1/A)-A-1 V=(q^p)._maxima_().rectform() after this, V._sage_() crashes, and I think it's the same crash as above. Transcribing what V is in maxima, we get: I*sin(atan2(0,q)*((1/A+1)*A-A-1))*abs(q)^((1/A+1)*A-A-1)+cos(atan2(0,q)*((1/A+1)*A-A-1))*abs(q)

[sage-devel] Re: Segmentation fault factoring a multivariate polynomial over IntegerModRing

2020-04-15 Thread Sebastian Oehms
> > It looks like this problem is going to be fixed by the upgrade to Singular > 4.1.3 (#25993). > Indeed! Thanks for pointing this out! > There is another segmentation fault related to the non-commutative > subsystem Plural, though, causing a doctest failure on the upgrade branch. > See htt

[sage-devel] Re: Segmentation fault factoring a multivariate polynomial over IntegerModRing

2020-04-14 Thread Markus Wageringel
It looks like this problem is going to be fixed by the upgrade to Singular 4.1.3 (#25993). sage: R. = Integers(7)[] sage: p = x**2-1 sage: p.factor() (x + 1) * (x + 6) There is another segmentation fault related to the non-commutative subsystem Plural, though, causing a doctest

[sage-devel] Re: segmentation fault in sage 7.3

2016-09-08 Thread Stan
I have both, one locally compiled version, which I upgraded from 7.x, and one freshly installed binary. Same problem on both. Seems that save_session() and load_session() causes all sorts of problems, especially when using jupyter. On Thursday, September 8, 2016 at 11:45:32 PM UTC+2, leif wrote

[sage-devel] Re: segmentation fault in sage 7.3

2016-09-08 Thread leif
Stan wrote: > Dear all, > > I am on debian jessy 64bit and after installing sage 7.3 Does that mean you took a pre-built binary, or did you build from source? -leif > I keep getting > segfault for the same worksheets that run smoothly in sage 6.8. I have > now managed to isolate a small exampl

[sage-devel] Re: Segmentation fault

2009-05-21 Thread Nick Alexander
> It works fine to do > sage: g = P2.division_points(19, poly_only=True) > which defines a polynomial of degree 361 over Q(sqrt(-87)), but then > g.roots() goes Boom. Me too. I've opened http://trac.sagemath.org/sage_trac/ticket/6113 Nick --~--~-~--~~~---~--~~

[sage-devel] Re: Segmentation fault

2009-05-21 Thread John Cremona
2009/5/21 John Cremona : > 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.| >