Bug 2057675
| Summary: | routine rebase of dyninst for rhel 9.1 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | William Cohen <wcohen> |
| Component: | dyninst | Assignee: | Stan Cox <scox> |
| dyninst sub component: | system-version | QA Contact: | Martin Cermak <mcermak> |
| Status: | CLOSED ERRATA | Docs Contact: | Jacob Taylor Valdez <jvaldez> |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | bstinson, fche, gfialova, jvaldez |
| Version: | 9.1 | Keywords: | FutureFeature, Rebase, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dyninst12.1.0-1.el9 | Doc Type: | Enhancement |
| Doc Text: |
.The `dyninst` packaged rebased to version 12.1
The `dyninst` package has been rebased to version 12.1. Notable bug fixes and enhancements include:
* Initial support for `glibc-2.35` multiple namespaces
* Concurrency fixes for DWARF parallel parsing
* Better support for the `CUDA` and `CDNA2` GPU binaries
* Better support for IBM POWER Systems (little endian) register access
* Better support for PIE binaries
* Corrected parsing for catch blocks
* Corrected access to 64-bit Arm (`aarch64`) floating point registers
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-15 10:14:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
William Cohen
2022-02-23 20:16:39 UTC
I see that we have a build ready for this: https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=18194 The soname bump caused us to fail repoclosure in CentOS Stream, though: https://composes.stream.centos.org/production/CentOS-Stream-9-20220426.0/logs/x86_64/repoclosure-AppStream.x86_64.log Do we need to coordinate a rebuild of systemtap? > Do we need to coordinate a rebuild of systemtap?
Coming by next Monday, if that's okay.
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 (dyninst bug fix and enhancement update), 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-2022:8058 |