Bug 1649465 - libcxxabi incompatible with libsupc++
Summary: libcxxabi incompatible with libsupc++
Alias: None
Product: Fedora
Classification: Fedora
Component: libcxxabi
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-13 16:24 UTC by Stas Sergeev
Modified: 2019-05-28 23:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-28 23:17:05 UTC
Type: Bug

Attachments (Terms of Use)
test case (638 bytes, application/x-gzip)
2018-11-13 16:24 UTC, Stas Sergeev
no flags Details

Description Stas Sergeev 2018-11-13 16:24:39 UTC
Created attachment 1505367 [details]
test case

Description of problem:
I am not really sure to whom to attribute this bug,
as too many components are involved. The problem starts
from the fact that mesa uses RTLD_GLOBAL to open various
libs, and some of them are written in C++, so they take
libstdc++ in. This leads to a crash when some other component
uses clang's libcxx. I filled the mesa bug already:

However, I suppose libcxxabi and libsupc++ should be
binary compatible, so there should be no crash when
they interfere. That's why I am also opening this bug.

See the attached test-case. Run "make", it will build
2 shlibs and "main" executable.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. make
2. ./main

Actual results:

Expected results:
no crash

Additional info:
I am not really sure if this is a bug here, or such
mix is not possible, in which case the bug is only in

Comment 1 Ben Cotton 2019-05-02 20:19:32 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-05-28 23:17:05 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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