Back to bug 1764235
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2019-10-22 13:58:50 UTC | Pool ID | sst_platform_tools_rhel_8 | |
| Carlos O'Donell | 2019-10-24 14:04:39 UTC | Assignee | glibc-bugzilla | codonell |
| Carlos O'Donell | 2019-10-25 01:27:49 UTC | Status | NEW | ASSIGNED |
| Carlos O'Donell | 2019-11-15 18:22:54 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | glibc-2.28-92 | |||
| errata-xmlrpc | 2019-11-16 21:55:44 UTC | Status | MODIFIED | ON_QA |
| Carlos O'Donell | 2020-01-07 20:37:28 UTC | Doc Text | A defect in the mtrace implementation could cause memory tracing to hang if certain internal functions failed. The mtrace memory tracing implemetnation has been made more robust to avoid the hang even in the face of internal failures. Users can now call mtrace and be assured that it completes in a bounded time even in the face of internal failures. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Sergey Kolosov | 2020-03-23 18:16:39 UTC | Status | ON_QA | VERIFIED |
| CC | skolosov | |||
| Petr Kovar | 2020-03-30 15:19:06 UTC | Docs Contact | zzoubkov | |
| Zuzana Zoubkova | 2020-04-02 13:00:53 UTC | Flags | needinfo?(codonell) | |
| Carlos O'Donell | 2020-04-02 13:35:56 UTC | Flags | needinfo?(codonell) | |
| Zuzana Zoubkova | 2020-04-02 16:06:17 UTC | Doc Text | A defect in the mtrace implementation could cause memory tracing to hang if certain internal functions failed. The mtrace memory tracing implemetnation has been made more robust to avoid the hang even in the face of internal failures. Users can now call mtrace and be assured that it completes in a bounded time even in the face of internal failures. | .`mtrace` no longer hangs when internal failures occur Previously, a defect in the `mtrace` implementation could cause memory tracing to hang. To fix this issue, the `mtrace` memory tracing implementation has been made more robust to avoid the hang even in the face of internal failures. As a result, users can now call `mtrace` and be assured that it completes in bounded time. |
| Zuzana Zoubkova | 2020-04-06 13:01:15 UTC | Doc Text | .`mtrace` no longer hangs when internal failures occur Previously, a defect in the `mtrace` implementation could cause memory tracing to hang. To fix this issue, the `mtrace` memory tracing implementation has been made more robust to avoid the hang even in the face of internal failures. As a result, users can now call `mtrace` and be assured that it completes in bounded time. | .`mtrace` no longer hangs when internal failures occur Previously, a defect in the `mtrace` tool implementation could cause memory tracing to hang. To fix this issue, the `mtrace` memory tracing implementation has been made more robust to avoid the hang even in the face of internal failures. As a result, users can now call `mtrace` and it no longer hangs, completing in bounded time. |
| errata-xmlrpc | 2020-04-28 00:32:53 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-04-28 16:50:19 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-04-28 16:50:19 UTC | |||
| errata-xmlrpc | 2020-04-28 16:50:46 UTC | Link ID | Red Hat Product Errata RHSA-2020:1828 | |
| Pavel Najman | 2021-09-17 12:19:35 UTC | Pool ID | sst_platform_tools_rhel_8 | sst_pt_gcc_glibc_rhel_8 |
| Red Hat One Jira (issues.redhat.com) | 2021-09-17 12:24:39 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-28584 | |
| 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 1764235