Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Previously, strace on s390x architecture couldn't handle the 31-bit binaries correctly. This has been fixed so that now there is a strace32 binary, which correctly handles 31-bit binaries even on s390x architecture.
Ah, never mind - see it's built as a separate subpackage on the compat arch.
On RHEL 5, we have:
<packagereq arch="ppc" type="mandatory">strace64</packagereq>
We could do the same for power & z on 6 and 7.
diff -u -u -r1.212 comps-rhel7.xml.in
--- comps-rhel7.xml.in 4 Oct 2012 20:14:33 -0000 1.212
+++ comps-rhel7.xml.in 15 Oct 2012 20:38:13 -0000
@@ -217,6 +217,8 @@
<packagereq type="default">smartmontools</packagereq>
<packagereq type="default">sos</packagereq>
<packagereq type="default">strace</packagereq>
+ <packagereq type="default" arch="ppc64">strace32</packagereq>
+ <packagereq type="default" arch="s390x">strace32</packagereq>
<packagereq type="default">subscription-manager</packagereq>
<packagereq type="default">sysstat</packagereq>
<packagereq type="default">systemtap-runtime</packagereq>
@@ -537,6 +539,8 @@
<packagereq type="mandatory">latrace</packagereq>
<packagereq type="mandatory">libreport-cli</packagereq>
<packagereq type="mandatory">strace</packagereq>
+ <packagereq type="mandatory" arch="ppc64">strace32</packagereq>
+ <packagereq type="mandatory" arch="s390x">strace32</packagereq>
<packagereq type="mandatory">systemtap-runtime</packagereq>
<packagereq type="default">abrt-addon-ccpp</packagereq>
<packagereq type="default">abrt-addon-python</packagereq>
as an example.
Hi,
I am creating a test plan for this Errata and it seems to me, that this bug and the "semtimedop" one ( https://bugzilla.redhat.com/show_bug.cgi?id=759566 ) are based on the same problem. Am I right? Can I test it the same way?
OLD = 4.5.19-1.11.el6_3.2
NEW = 4.5.19-1.17.el6
so I run the strace, both OLD and NEW on:
1) semtimedop_app compiled with "-m31" and both fails:
semtimedop(4393752297474, 0x3ff7fdcc1ca, 4393751543809, {...}) = -1 EAGAIN (Resource temporarily unavailable)
2) semtimedop_app compiled normally, 64bit and both are OK:
semtimedop(688130, {{0, -1, 0}}, 1, {0, 0}) = -1 EAGAIN (Resource temporarily unavailable)
-----
Then I run the strace32 (NEW, because OLD does not exist) on semtimedop_app compiled with "-m31" and it runs well:
semtimedop(851970, {{0, -1, 0}}, 1, {0, 0}) = -1 EAGAIN (Resource temporarily unavailable)
-----
So it seems to me, that the strace32 works well on 31 bit apps with semtimedop and also others syscalls and the 64bit strace does not, but it is planned and expectable. So I should test somehow that the strace32 is present in the update and decodes well the 31bit app with semtimedop call or whatever else and not to care about the "normal" strace and its compatibility with 31bit apps.
Is it like this?
Thanks.
Michael
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.
http://rhn.redhat.com/errata/RHBA-2013-0282.html
Ah, never mind - see it's built as a separate subpackage on the compat arch. On RHEL 5, we have: <packagereq arch="ppc" type="mandatory">strace64</packagereq> We could do the same for power & z on 6 and 7. diff -u -u -r1.212 comps-rhel7.xml.in --- comps-rhel7.xml.in 4 Oct 2012 20:14:33 -0000 1.212 +++ comps-rhel7.xml.in 15 Oct 2012 20:38:13 -0000 @@ -217,6 +217,8 @@ <packagereq type="default">smartmontools</packagereq> <packagereq type="default">sos</packagereq> <packagereq type="default">strace</packagereq> + <packagereq type="default" arch="ppc64">strace32</packagereq> + <packagereq type="default" arch="s390x">strace32</packagereq> <packagereq type="default">subscription-manager</packagereq> <packagereq type="default">sysstat</packagereq> <packagereq type="default">systemtap-runtime</packagereq> @@ -537,6 +539,8 @@ <packagereq type="mandatory">latrace</packagereq> <packagereq type="mandatory">libreport-cli</packagereq> <packagereq type="mandatory">strace</packagereq> + <packagereq type="mandatory" arch="ppc64">strace32</packagereq> + <packagereq type="mandatory" arch="s390x">strace32</packagereq> <packagereq type="mandatory">systemtap-runtime</packagereq> <packagereq type="default">abrt-addon-ccpp</packagereq> <packagereq type="default">abrt-addon-python</packagereq> as an example.