RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1375711 - std::rethrow_exception is not properly incrementing the uncaught exception count
Summary: std::rethrow_exception is not properly incrementing the uncaught exception count
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcc
Version: 7.2
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: Michael Petlan
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1380760 1390370
TreeView+ depends on / blocked
 
Reported: 2016-09-13 19:47 UTC by John Walter
Modified: 2020-09-10 09:47 UTC (History)
11 users (show)

Fixed In Version: gcc-4.8.5-12.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1380760 (view as bug list)
Environment:
Last Closed: 2017-08-01 22:35:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 62258 0 None None None 2016-09-13 19:47:33 UTC
Red Hat Product Errata RHBA-2017:2094 0 normal SHIPPED_LIVE gcc bug fix update 2017-08-01 19:36:07 UTC

Description John Walter 2016-09-13 19:47:33 UTC
Description of problem:
Calls to `std::uncaught_exception` after calling
`std::rethrow_exception' always return `true' when
`std::uncaught_exception' should return `false' unless an exception is
in flight. `std::rethrow_exception' does not update
`__cxa_eh_globals::uncaughtExceptions' while the following call to
`__cxa_begin_catch' decrements it. This fixes PR 62258.


How reproducible:
Always


Additional info:
PATCH ==> https://gcc.gnu.org/ml/libstdc++/2015-02/msg00005.html


This is a two-line patch that is already fixed upstream.

Comment 6 Rob Riggs 2016-09-22 14:58:30 UTC
Affects RHEL 6.7 as well.  Probably introduced here in RHEL6

* Tue Apr 15 2014 Marek Polacek <polacek> 4.4.7-5
- fix std::uncaught_exception (#1085442, PR c++/59224)

as a side-effect since the problem does not manifest with libstdc++-4.4.7-3.

This is an issue when using devtoolset compilers on RHEL6, esp. when using C++11 std::future with exceptions, which uses std::rethrow_exception() to move the exceptions across threads.

Comment 19 Michael Petlan 2017-05-31 14:06:37 UTC
The related test passes on all architectures with gcc-4.8.5-14.el7.
VERIFIED.

Comment 20 errata-xmlrpc 2017-08-01 22:35:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2094


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