Ask Your Question
4

where to report bugs found using systems used by sage?

asked 2018-07-10 14:51:00 -0500

Nasser gravatar image

updated 2018-07-11 18:28:14 -0500

I am finding lots of bugs in systems used by sageMath. So not sure if I should report them to sagebug tracking as I have been doing, or to the other systems. The problem I can't find a place to report them for the other systems.

For example

>sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 8.3.rc0, Release Date: 2018-07-08                 │
│ Type "notebook()" for the browser-based notebook interface.        │
│ Type "help()" for help.                                            │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable.     ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: var('x d a c b')
(x, d, a, c, b)
sage: integrate(sqrt(d*x^2 + e*x + c)*sqrt((b*x^2 + a)^2)/x^4,x, algorithm="giac")
Giac crashed -- automatically restarting.
sage0*x

#another bug. Just Added also as new comment ticket
# at  https://trac.sagemath.org/ticket/25822

sage: var('x g b f n c a d');
sage: integrate(1/((g*x + f)^2*(b*log((e*x + d)^n*c) + a)^3),x, algorithm="giac")
Done

I searched and searched, and can't find even a forum for Giac or a place to report a bug. is giac even supported system? I went to https://www-fourier.ujf-grenoble.fr/~... and I see no place to report bugs. I clicked on the forum link there, but it is dead link.

Same for Maxima. I can't find where to report bugs found it is when using sagemath.

┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 8.3.rc0, Release Date: 2018-07-08                 │
│ Type "notebook()" for the browser-based notebook interface.        │
│ Type "help()" for help.                                            │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable.     ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

var('x')
integrate(log(sin(x))*sin(x)^2,x)

;;;
;;; Detected access to protected memory, also kwown as 'bus or segmentation fault'.
;;; Jumping to the outermost toplevel prompt
;;;

I once send email about a different maxima bug to maxima-bugs@lists.sourceforge.net but never heared back and I do not see it posted on anywhere on sourceforge. I do not think any one reads these.

May be sagemath should have an OFFICIAL web page, listing the exact location of where to report bugs found in systems used by sagemath if they are not to be reported to sagemath bug database?

edit retag flag offensive close merge delete

Comments

1

This forum is a good place to post a bug report. An alternative is to use the sage-devel mailing list.

vdelecroix gravatar imagevdelecroix ( 2018-07-10 15:01:13 -0500 )edit
1

For maxima, bug tracking happens on https://sourceforge.net/p/maxima/bugs/ . It's not super-active but every now and again there is some activity there. I think it's the best place to report maxima bugs. Of course a report there should be about maxima, without involvement of sage. It's fine to have sage-trac tickets tracking sage-discovered maxima bugs, but you'd help fixing them if you can extract the erroneous maxima behaviour (often this is a near-automatic procedure).

nbruin gravatar imagenbruin ( 2018-07-10 15:59:23 -0500 )edit
1

For Giac, it seems the link to the forum is currently broken, probably due to the host university recently changing name from "Université Joseph Fourier" to "Université Grenoble Alpes", and correspondingly changing domain name from ujf-grenoble.fr to univ-grenoble-alpes.fr.

In the meantime, you could email a bug report to the main developer. In this case, I sent him an email with a link to this Ask Sage question, to alert him both to the bug you found and to the broken link.

slelievre gravatar imageslelievre ( 2018-07-11 04:38:46 -0500 )edit
1

The Giac bug is now fixed upstream, but not in a stable release. The reference for the upstream fix is "Geogebra svn 62822". Since Geogebra uses Giac, the Giac source code is under version control using Subversion (svn) at Geogebra:

The links to the Giac/Xcas forum have been fixed on the Giac/Xcas home page.

Thanks for alerting to this bug and to the broken links!

slelievre gravatar imageslelievre ( 2018-07-11 09:35:04 -0500 )edit

2 answers

Sort by » oldest newest most voted
3

answered 2018-07-11 04:32:58 -0500

slelievre gravatar image

How to report bugs in other systems found via their use in SageMath is an excellent question.

One of the aspects is whether it is a bug in the other system, or in the Sage interface to it.

In case of doubt, the best is to report on the Sage side, at Ask Sage, sage-support, or sage-devel. Then others can help determine if the bug is from the other system or from the interface.

For bugs that definitely belong to the other system, ideally one should try to reproduce directly (without using Sage), in order to report them "upstream" (which means to the other system that Sage uses).

If the bug is reported on both sides, it's good to cross-link the bug reports.

edit flag offensive delete link more
4

answered 2018-07-11 06:00:41 -0500

tmonteil gravatar image

updated 2018-07-11 11:01:39 -0500

slelievre gravatar image

Here are some points:

  • https://ask.sagemath.org is a good place to report such bugs (especially for newcomers who might be impressed by opening a ticket),
  • then someone (the same person or possibly someone else) should open a ticket on https://trac.sagemath.org even if they know that the problem comes from an upstream library,
  • then someone (else or not) should report upstream and modify the trac field "Report Upstream" to "Reported upstream, no feedback yet". It is better if the commands leading to the error are typed directly on upstream's interface, so that it is clear for upstream that it is not an issue with the SageMath interface, and so that they can reproduce it easily,
  • the "Report Upstream" field should be updated ("Developers acknowledge bug", etc) until the problem is fixed upstream [particular case: if upstream developers deny it's a bug, then we have to patch ourselves],
  • when we got the fix (usually after a package update), we add a doctest on the ticket so that if the problem reappears, then we could immediately see the regression (not all upstream libraries have a testing framework). In your particular case, it is also interesting to compare the result with other algorithms.

Compared to only reporting upstream, this workflow ensures tracking on the SageMath side.

Regarding the issues in the question, thanks for reporting, the two issues are now tracked as Sage Trac ticket 25822 and Sage Trac ticket 25823.

Do not hesitate to modify the tickets, report upstream, follow the history, and write a doctest that will benefit both Sage and Giac or Maxima!

Regarding the place to report upstream bugs for each library, there is an Upstream Contact field on the SPKG.txt file of each package directory, which is SAGE_ROOT/build/pkgs/<package_name>, and can be browsed online at:

edit flag offensive delete link more

Comments

Hello. fyti, Bug 25823 (Maxima causing sage to core dump) I already entered 3 weeks ago in sage tracking. Here it is https://trac.sagemath.org/ticket/25636 The core dump happens on more than one integral. I add them all to #25636 each time I find a new one.

Nasser gravatar imageNasser ( 2018-07-11 18:26:22 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-07-10 14:51:00 -0500

Seen: 81 times

Last updated: Jul 11