Bug 1398393
| Summary: | Rebase systemtap to 3.x | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mbenitez |
| Component: | systemtap | Assignee: | Frank Ch. Eigler <fche> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
| Severity: | unspecified | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | bgollahe, fche, jbastian, jistone, lberk, mcermak, mjw, mnewsome, pbunyan |
| Target Milestone: | alpha | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemtap-3.1-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
_systemtap_ rebased to version 3.1
The _systemtap_ package has been upgraded to upstream version 3.1, which provides a number of bug fixes and enhancements over the previous version. Notable changes include:
* The probes for system calls no longer default to being based on *debuginfo* information.
* Support for probing *Python* functions has been added.
* Access to *Java* function parameters has been made more uniform.
* The performance of statistical aggregate variables has been improved.
* A new statistics operator "@variance" has been added.
* More options for fetching and setting user-space values have been added.
* NFS monitoring has been improved with sample
scripts and tapset compatibility fixes.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 09:34:40 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1386120, 1390370, 1411714, 1465627 | ||
|
Description
mbenitez
2016-11-24 16:44:06 UTC
Rebase testing systemtap-3.1-3.el7 finished. lgtm, thanks 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:2301 |