Back to bug 1663035

Who When What Removed Added
Florian Weimer 2019-01-02 19:28:53 UTC Link ID Sourceware 24018
Martin Cermak 2019-02-27 15:20:07 UTC CC mcermak
Carlos O'Donell 2019-03-01 15:45:52 UTC Blocks 1684553
Matt Newsome 2019-03-08 17:30:22 UTC Blocks 1684553
Stef Walter 2019-03-16 07:57:57 UTC Depends On 1682593
Carlos O'Donell 2019-04-12 13:31:53 UTC Assignee glibc-bugzilla ashankar
Carlos O'Donell 2019-04-13 05:15:41 UTC Deadline 2019-05-03
Brendan Conoboy 2019-04-17 19:19:44 UTC Blocks 1701002
Carlos O'Donell 2019-04-23 21:48:22 UTC Deadline 2019-05-03 2019-05-08
Arjun Shankar 2019-04-26 14:53:01 UTC Status ASSIGNED MODIFIED
Fixed In Version glibc-2.28-52.el8
errata-xmlrpc 2019-05-08 22:31:18 UTC Status MODIFIED ON_QA
Carlos O'Donell 2019-05-14 17:17:26 UTC Doc Text Cause: A defect in the gettext function could result in a return value of NULL in certain low-memory situations.

Consequence: The gettext function is never expected to return NULL. Upon failure the gettext function should return the untranslated string it received as input.

Fix: The gettext function is corrected to return the untranslated string when internal operations run out of memory.

Result: The gettext function now follows the documented API even under certain low-memory conditions.
Doc Type If docs needed, set a value Bug Fix
Carlos O'Donell 2019-05-15 16:10:19 UTC Blocks 1684553
Matt Newsome 2019-06-17 11:36:47 UTC Blocks 1721112
Matt Newsome 2019-06-17 11:37:40 UTC Blocks 1721112
Florian Weimer 2019-06-20 13:56:05 UTC Target Release 8.0 8.1
Vladimír Slávik 2019-07-12 16:00:12 UTC CC vslavik
Docs Contact vslavik
Vladimír Slávik 2019-08-16 14:56:45 UTC Doc Text Cause: A defect in the gettext function could result in a return value of NULL in certain low-memory situations.

Consequence: The gettext function is never expected to return NULL. Upon failure the gettext function should return the untranslated string it received as input.

Fix: The gettext function is corrected to return the untranslated string when internal operations run out of memory.

Result: The gettext function now follows the documented API even under certain low-memory conditions.
.`gettext` returns text even when out of memory

Previously, when out of memory, the `gettext` function for text localization could erroneously return a NULL value instead of untranslated text. As a consequence, applications could unexpectedly lack text output or labels. The behavior was changed so that `gettext` returns text even if out of memory.
Flags needinfo?(ashankar)
Arjun Shankar 2019-08-20 15:55:07 UTC Flags needinfo?(ashankar)
Vladimír Slávik 2019-08-22 18:08:58 UTC Doc Text .`gettext` returns text even when out of memory

Previously, when out of memory, the `gettext` function for text localization could erroneously return a NULL value instead of untranslated text. As a consequence, applications could unexpectedly lack text output or labels. The behavior was changed so that `gettext` returns text even if out of memory.
.`gettext` returns untranslated text even when out of memory

Previously, when out of memory, the `gettext` function for text localization could erroneously return a NULL value instead of untranslated text. As a consequence, applications could unexpectedly lack text output or labels. The behavior was changed so that `gettext` returns text even if out of memory.
Sergey Kolosov 2019-08-28 15:05:58 UTC Status ON_QA VERIFIED
CC skolosov
Lucie Vařáková 2019-09-09 10:16:18 UTC CC lmanasko
Docs Contact vslavik ajamaiya
Abhimanyu Jamaiyar 2019-09-17 11:29:55 UTC Doc Text .`gettext` returns untranslated text even when out of memory

Previously, when out of memory, the `gettext` function for text localization could erroneously return a NULL value instead of untranslated text. As a consequence, applications could unexpectedly lack text output or labels. The behavior was changed so that `gettext` returns text even if out of memory.
.The `gettext()` function returned untranslated text when out of memory

Previously, the `gettext()` function for text localization returned the NULL value instead of text when out of memory, resulting in applications lacking text output or labels. The bug has been fixed and now, `gettext()` - returns untranslated text when out of memory as expected.
Flags needinfo?(ashankar)
Arjun Shankar 2019-09-26 11:17:29 UTC Flags needinfo?(ashankar)
Abhimanyu Jamaiyar 2019-09-26 12:15:27 UTC Doc Text .The `gettext()` function returned untranslated text when out of memory

Previously, the `gettext()` function for text localization returned the NULL value instead of text when out of memory, resulting in applications lacking text output or labels. The bug has been fixed and now, `gettext()` - returns untranslated text when out of memory as expected.
.`gettext` returns untranslated text even when out of memory

Previously, the `gettext()` function for text localization returned the NULL value instead of text when out of memory, resulting in applications lacking text output or labels. The bug has been fixed and now, `gettext()` - returns untranslated text when out of memory as expected.
Flags needinfo?(ashankar)
Arjun Shankar 2019-09-26 18:49:55 UTC Flags needinfo?(ashankar)
errata-xmlrpc 2019-11-05 00:10:14 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2019-11-05 21:29:04 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2019-11-05 21:29:04 UTC
errata-xmlrpc 2019-11-05 21:29:25 UTC Link ID Red Hat Product Errata RHSA-2019:3513
Red Hat One Jira (issues.redhat.com) 2020-11-14 16:26:47 UTC Link ID Red Hat Issue Tracker - Private RHELPLAN-13183
Pavel Najman 2021-09-17 12:17:42 UTC Pool ID sst_platform_tools_rhel_8 sst_pt_gcc_glibc_rhel_8
Mark O'Brien 2023-07-18 14:30:35 UTC Pool ID sst_pt_glibc_rhel_8 sst_pt_libraries_rhel_8

Back to bug 1663035