Bug 1711374 - runtime crashes when built with -D_GLIBC_ASSERTIONS
Summary: runtime crashes when built with -D_GLIBC_ASSERTIONS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: giac
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Antonio T. (sagitter)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-17 15:59 UTC by Frederic Han
Modified: 2019-05-29 02:59 UTC (History)
2 users (show)

Fixed In Version: giac-1.5.0.53-1.fc30 giac-1.5.0.53-1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-27 01:02:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fix for giac <1.5.0.53 (2.48 KB, patch)
2019-05-17 15:59 UTC, Frederic Han
no flags Details | Diff
Fixes changes in the testsuite due to pari 2.11 and later. (779 bytes, patch)
2019-05-17 16:07 UTC, Frederic Han
no flags Details | Diff

Description Frederic Han 2019-05-17 15:59:09 UTC
Created attachment 1570167 [details]
Fix for giac <1.5.0.53

Description of problem:
The giac packages built with -D_GLIBC_ASSERTIONS gives crashes at run time. But this flag looks defined by default since fc28. 

Version-Release number of selected component (if applicable):
all giac versions <1.5.0.53  on fc28 and later

How reproducible:
anytime  on  x86_64, not tested on other arch.

Steps to Reproduce:
1. launch the program icas and try
2. ifactor(10**40+68)

Actual results:
0>> ifactor(10**40+68)
/usr/include/c++/8/bits/stl_vector.h:932: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = giac::basis_t; _Alloc = std::allocator<giac::basis_t>; std::vector<_Tp, _Alloc>::reference = giac::basis_t&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
Aborted (core dumped)


Expected results:
0>> ifactor(10**40+68)
2^2*3*19391*3575030373429491*12020950579264347719

Additional info:
This is fixed in upstream source 1.5.0-53
or with the following patch.

Comment 1 Frederic Han 2019-05-17 16:07:18 UTC
Created attachment 1570168 [details]
Fixes changes in the testsuite due to pari 2.11 and later.

The patch giac-testsuite_pari_2.11.patch 
allowed me to run the test suite without errors (on x86_64). (Some outputs are different when giac is built with pari versions >2.11

Comment 2 Fedora Update System 2019-05-18 14:24:24 UTC
giac-1.5.0.53-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-dee9e49f52

Comment 3 Fedora Update System 2019-05-18 14:24:28 UTC
giac-1.5.0.53-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e7d4d11851

Comment 4 Fedora Update System 2019-05-19 00:51:35 UTC
giac-1.5.0.53-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-dee9e49f52

Comment 5 Fedora Update System 2019-05-19 10:49:53 UTC
giac-1.5.0.53-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e7d4d11851

Comment 6 Fedora Update System 2019-05-27 01:02:17 UTC
giac-1.5.0.53-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2019-05-29 02:59:21 UTC
giac-1.5.0.53-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.