-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
integral of ln(1+4/5*sin(x)) from -3.1415 to 3.1415 crashes Maxima and Sage #13097
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Could it rather be something wrong in how we are receiving data from Maxima(lib)? |
comment:4
I don't think maxima understands
you see the same thing happening. No problem in vanilla maxima. But when we load
FYI: with
you see what expression gets passed to maxima_lib. With
you see what maxima's parser would produce. With
you can trigger the same explosion. Note that with this trick, you can quickly see that
creates an essentially different expression. |
comment:5
The problem can be simplified to
which maxima without This is now Maxima Artifact 3533723 |
Upstream: Reported upstream. No feedback yet. |
comment:6
Well, egg on my face! Sorry for that noise. I just don't use Maxima enough beyond trying to generate bug reports or find new functionality for Sage :) And good diagnosis; I guess if I had tried |
comment:7
Replying to @nbruin:
facepalm. Sorry for noise on |
Changed upstream from Reported upstream. No feedback yet. to Reported upstream. Developers acknowledge bug. |
comment:8
We really need more options for "upstream" ;-). How about "Developers acknowledge bug, propose fix, but haven't gotten around to merging it because they got the fix with less than 24 hours round trip time"? See Maxima tracker. I have no doubt this will be fixed in some future Maxima release. |
comment:9
We can monkey-patch Barton Willis's fix into sage's maxima:
This just patches a routine defined in |
Changed upstream from Reported upstream. Developers acknowledge bug. to Fixed upstream, but not in a stable release. |
Changed keywords from none to integral |
comment:16
I don't see crashes 8 years later on:
propose to close as worksforme. |
comment:17
ok, then |
comment:18
As always, doctest ... |
comment:19
Also, it was indeed applied in Maxima. |
Changed upstream from Fixed upstream, but not in a stable release. to Fixed upstream, in a later stable release. |
comment:20
ok, you are right, but I will wait until #25119 is in sage |
comment:21
obviously no rush whatsoever since it's fixed |
Branch: public/13097 |
comment:23
The PR adds the original issue as a doctest. New commits:
|
Author: Dave Morris |
Commit: |
comment:24
Thanks! |
Reviewer: Karl-Dieter Crisman |
Changed branch from public/13097 to |
See extensive discussion at this sage-support thread.
Reported by Ben Jones:
There don't seem to be any problems with Maxima. Although it's been traced down (thanks to Dan Drake) to 5.0.beta3, the only obvious candidate for a change in our interface is when we added
abs_integrate
, which doesn't seem to impact things.And we have
so something must indeed be wrong in how we're sending this to Maxima.
Upstream: Fixed upstream, in a later stable release.
CC: @benjaminfjones @sagetrac-dsm
Component: calculus
Keywords: integral
Author: Dave Morris
Branch/Commit:
3f41b09
Reviewer: Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/13097
The text was updated successfully, but these errors were encountered: