Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#49969 - [wxmaxima] Segfault when loading older saved files
Attached to Project:
Arch Linux
Opened by anonymous archuser (bugaboo) - Wednesday, 06 July 2016, 11:24 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 06 July 2016, 17:40 GMT
Opened by anonymous archuser (bugaboo) - Wednesday, 06 July 2016, 11:24 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 06 July 2016, 17:40 GMT
|
DetailsDescription:
wxMaxima crashes with a segfault when loading older saved files. Additional info: * package version(s): 16.04.2-1 x64 * config and/or log files etc: only a segfault Steps to reproduce: If opened with a double click or simply "wxmaxima" from the terminal, it complains about an ABI mismatch (1009 vs 1010), it opens up fine, can work with it, can save, both .wxm and .wxmx, can load them, but when I try to load older saves (like the one in the attachment), it crashes with a segfault. If run from console with "wxmaxima -o Bessel.wxm", there's the same ABI mismatch, then, immediately it crashes and sbcl starts flooding the terminal. I need to "killall -9 sbcl"; there are hundreds, if not thousands of lines in there. Downgrading to 16.04.0-1 works and seems stable. This is since the newest upgrade after 16.04.0-1. I went to #archlinux and talked to a few over there, they suggested to build wxMaxima with debugging enabled, I did, with their help I used it with gdb, which pointed to MathCell.cpp, "tmp->ClearCache()", line 100 and something. I don't have the debug version, anymore. As a side note, the update to wxMaxima came with Codeblocks, as well, which also complained about the same ABI mismatch and crashed immediately with its bug report window. The latest update to CB seems to have the same ABI complaint, but it works now. CB could also be downgraded, but the debugger seemed to take forever for "next instruction". Just so you don't get the wrong ideas, I am only just learning C++... If there's anything else that I can do, please let me know. |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 06 July 2016, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: wxmaxima 16.04.2-2
Wednesday, 06 July 2016, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: wxmaxima 16.04.2-2
Comment by Antonio Rojas (arojas) -
Wednesday, 06 July 2016, 17:21 GMT
wxmaxima 16.04.0 compiled with gcc6 is also affected, while 16.04.2 compiled with clang is ok. So this is clearly triggered by GCC 6. Please report it upstream.
Comment by Antonio Rojas (arojas) -
Wednesday, 06 July 2016, 17:40 GMT
Added workaround in 16.04.2-2. Still, please report it upstream so that they fix it properly.
Bessel.wxm