Description of problem: maxima killed by SIGSEGV Version-Release number of selected component (if applicable): 5.45.1-3.fc37.x86_64 How reproducible: always Steps to Reproduce: 1. run `maxima` Actual results: Segmentation fault (core dumped) Expected results: A running maxima session. Additional info: I was unable to report the bug automatically: --- Running report_uReport --- Server responded with an error: 'Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing' ('report_uReport' exited with 1) Installing a different maxima runtime (I tested maxima-runtime-clisp, the default seems to be sbcl), and running with `maxima -l clisp` succeeds without a segfault.
After reading https://maxima.sourceforge.io/lisp.html I tried out just running `rmaxima`--which succeeded. $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (SBCL for F36?) Listing available runtimes still makes it crash: $ rmaxima --list-avail rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). rlwrap itself has not crashed, but for transparency, it will now kill itself with the same signal warnings can be silenced by the --no-warnings (-n) option But it stopped working after running the following session: $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (%i1) 1+1 1+1 Maxima encountered a Lisp error: parser: end of file while scanning expression. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Now all I get is: $ rmaxima rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). rlwrap itself has not crashed, but for transparency, it will now kill itself with the same signal warnings can be silenced by the --no-warnings (-n) option
More data points: running in a fresh F37 toolbox yields $ maxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (again, SBCL claims to be compiled for F36?) No crashes after running a similar session as in my other comment for `rmaxima`. My installed F37 (for which I created the original bug report) has been initially installed as F37-beta.
(In reply to René Kraneis from comment #1) > Now all I get is: > $ rmaxima > > rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). > rlwrap itself has not crashed, but for transparency, > it will now kill itself with the same signal > > warnings can be silenced by the --no-warnings (-n) option I randomly do get a working session: $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. Statistics for the nth run of `rmaxima`, that did not lead to SIGSEGV: sum: 101 min: 1 max: 20 median: 3.5 average: 5.6 Some fuzzing around shows, that the same is true for just running `maxima`, it was just by chance, that `rmaxima` succeeded on first try. I have no idea, what's going on and don't see this behavior in my F37 toolbox.