Description of problem: Entering leads to an immediate segmentation fault. Version-Release number of selected component (if applicable): 1.9.0.29 How reproducible: Always Steps to Reproduce: 1.Try to run "giac" 2. 3. Actual results: Segmentation fault Expected results: giac prompt ">" Additional info: Output from running "icas" in GDB: 0x00005555556aa5ee in nlr_push (nlr=<synthetic pointer>) at ../micropython-1.12/xcas/../py/nlrx64.c:60 60 __asm volatile ( (gdb) bt #0 0x00005555556aa5ee in nlr_push (nlr=<synthetic pointer>) at ../micropython-1.12/xcas/../py/nlrx64.c:60 #1 micropy_eval (str=0x55555577bfc4 "1") at ../micropython-1.12/xcas/main.c:495 #2 micropy_ck_eval (line=0x55555577bfc4 "1") at /usr/src/debug/giac-1.9.0.29-1.fc37.x86_64/src/Python.cc:42 #3 0x00005555555a88aa in _sub_I_65535_0.0 () #4 0x00007ffff5a4a63e in call_init (env=<optimized out>, argv=0x7fffffffd4c8, argc=1) at ../csu/libc-start.c:145 #5 __libc_start_main_impl (main=0x5555555a39a0 <main(int, char**)>, argc=1, argv=0x7fffffffd4c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd4b8) at ../csu/libc-start.c:368 #6 0x00005555555aade5 in _start ()
Thank you for reporting this issue. Opened a bug ticket to upstream forum.
(In reply to Antonio T. sagitter from comment #1) > Thank you for reporting this issue. > Opened a bug ticket to upstream forum. Thanks, I've gone to that site and saw them saying (basically) that a backtrace isn't all that helpful to them. They seemed to think I was stepping through the program whne I was not. I just let it in in GDB, creating the backtrace when the program crashed.
Hi I have tried the following: (NB upgrading to latest sources giac 1.9.0.33 didn't help) mock -r fedora-rawhide-x86_64 --no-clean https://kojipkgs.fedoraproject.org//packages/giac/1.9.0.29/2.fc38/src/giac-1.9.0.29-2.fc38.src.rpm mock -r fedora-rawhide-x86_64 --shell cd build/BUILD/giac-1.9.0/ then src/icas was also crashing but something is strange with the automatic built of the package because if I just do: make clean export RPM_ARCH=x86_64 export RPM_PACKAGE_RELEASE=1.9.0.29 export RPM_PACKAGE_VERSION=2 export RPM_PACKAGE_NAME=giac make (so without reconfiguring anything) then src/icas was not crashing and I could do some computations. But I don't understand the difference between this and the built from rpmbuild. Any idea? Anyways I have also tried to build the package with adding --enable-micropy=no in %configure in giac.spec and it also removed the starting crash.
(In reply to Frederic Han from comment #3) > Hi I have tried the following: > (NB upgrading to latest sources giac 1.9.0.33 didn't help) > mock -r fedora-rawhide-x86_64 --no-clean > https://kojipkgs.fedoraproject.org//packages/giac/1.9.0.29/2.fc38/src/giac-1. > 9.0.29-2.fc38.src.rpm > mock -r fedora-rawhide-x86_64 --shell > cd build/BUILD/giac-1.9.0/ > > then src/icas was also crashing > but something is strange with the automatic built of the package because if > I just do: > make clean > export RPM_ARCH=x86_64 > export RPM_PACKAGE_RELEASE=1.9.0.29 > export RPM_PACKAGE_VERSION=2 > export RPM_PACKAGE_NAME=giac > make > (so without reconfiguring anything) > then src/icas was not crashing and I could do some computations. > > But I don't understand the difference between this and the built from > rpmbuild. Any idea? Include two patches for this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2151473 > > Anyways I have also tried to build the package with adding > --enable-micropy=no in %configure in giac.spec > and it also removed the starting crash.
Thank you, I have reported it upstream: https://xcas.univ-grenoble-alpes.fr/forum/viewtopic.php?f=5&t=2829&p=12654#p12654
Hi there, So we're waiting for a patch to be applied upstream?
But isn't the package 1.9.0.29-2 already containing these 2 patches? Because I still have the starting crash. (that's why I missed them)
FEDORA-2023-34494057fd has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-34494057fd
FEDORA-2023-4ed82e36b7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4ed82e36b7
FEDORA-2023-4ed82e36b7 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-4ed82e36b7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4ed82e36b7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-34494057fd has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-34494057fd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-34494057fd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
@Frederic, can you try with this new build? I disabled LTO flags and i do not obtain any crash. https://koji.fedoraproject.org/koji/taskinfo?taskID=95877237
Hi Antonio, I built the "-2" version from a SRPM and tried it and it failed to run. I just tried the "-3" version and it does start. So, "Working!" -David
Thank you David
So, put the "-3" version out to release and close this bug?
-3 looks good to me also (I tried the fc37 binary under mock with icas + install giacpy and I was able to run the giacpy doctests without PB) Thank you Frederic
FEDORA-2023-4ed82e36b7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-34494057fd has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-97628ed283 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-97628ed283
FEDORA-2023-97628ed283 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-97628ed283` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-97628ed283 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-241e2dca83 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-241e2dca83` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-241e2dca83 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-241e2dca83 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-97628ed283 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.