Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plot of rational function crashes sage #10684

Closed
aghitza opened this issue Jan 25, 2011 · 7 comments
Closed

plot of rational function crashes sage #10684

aghitza opened this issue Jan 25, 2011 · 7 comments

Comments

@aghitza
Copy link

aghitza commented Jan 25, 2011

In sage-4.6.1, the following plot command results in a crash:

sage: plot(lambda x: 1/(x^2-0.5^2), (-10, 10), ymin=-5, ymax=5)
/opt/sage/local/bin/sage-sage: line 300:  5596 Illegal instruction      (core dumped) sage-ipython "$@" -i

Note that the following modified version works fine:

sage: plot(lambda x: 1/(x^2-1^2), (-10, 10), ymin=-5, ymax=5)

CC: @jasongrout

Component: graphics

Keywords: plot rational function crash

Issue created by migration from https://trac.sagemath.org/ticket/10684

@a-andre
Copy link

a-andre commented Jan 25, 2011

comment:1

I cannot confirm this crash. Tested with 4.6.2.alpha0.

@sagetrac-robert-goss
Copy link
Mannequin

sagetrac-robert-goss mannequin commented Feb 8, 2011

comment:3

I cannot confirm this crash either. Testing with 4.6.1 release

@jasongrout
Copy link
Member

comment:4

I also didn't get a crash for the first plot (OSX 10.6.6, sage-4.6.1). Alex, can you provide more details about your setup?

@aghitza
Copy link
Author

aghitza commented Feb 9, 2011

comment:5

Hmmm. This ticket should definitely be closed as invalid.

I don't actually know what happened. The machine I got this on runs Arch Linux and is rather slow for building sage from scratch, so I have been using the binaries packaged with Arch. Since I ran into the problem there have been a couple of updates for these binaries so maybe something was slightly off and is now ok. Or maybe something else was messed up in my setup and now is back to normal. In any case, I cannot reproduce this anymore.

If someone is really keen on doing detective work on this, I could probably downgrade my sage binaries and try to catch this again.

@jasongrout
Copy link
Member

comment:6

What do you say we mark it as invalid, with the understanding that you open it again if you see it again. My first inclination is that the binary was built on a processor using processor-specific functionality that your processor did not have. That seems to usually be the cause of the error messages you saw.

@jasongrout
Copy link
Member

comment:7

I meant, what do you think about marking this ticket as invalid now and opening another one if you see the problem again.

@aghitza
Copy link
Author

aghitza commented Feb 10, 2011

comment:8

Sounds good.

@aghitza aghitza closed this as completed Feb 10, 2011
@sagetrac-mvngu sagetrac-mvngu mannequin removed this from the sage-4.7 milestone Feb 10, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants