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.
Cause
The cmdline_string() function used to concatenate commandline arguments
would abort the concatenation when it encountered a NULL pointer for an
argument.
Consequence
The cmdline_string() function would not print any arguments following
a null argument.
Fix
The cmdline_string() function insert "" for empty string.
Result
The cmdline_args() function now prints all arguments from the command
line including ones that follow a NULL argument.
Created attachment 474525[details]
cmdlinefail.stp
Description of problem:
In tapset context.stp, cmdline_args won't return data after the first NULL argument.
Version-Release number of selected component (if applicable):
systemtap-1.2-9.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. stap cmdlinefail.stp (see attached file)
2. In a separate window, execute: /bin/ls "" additional arguments
3. Look at stap output
Actual results:
stap displays: /bin/ls
Expected results:
stap displays: /bin/ls ^@ additional arguments
Note, that instead of ^@, it could display something else, or even nothing, but it should display the additional arguments.
Additional info:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
The cmdline_string() function used to concatenate commandline arguments
would abort the concatenation when it encountered a NULL pointer for an
argument.
Consequence
The cmdline_string() function would not print any arguments following
a null argument.
Fix
The cmdline_string() function insert "" for empty string.
Result
The cmdline_args() function now prints all arguments from the command
line including ones that follow a NULL argument.
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-2011-1517.html
Created attachment 474525 [details] cmdlinefail.stp Description of problem: In tapset context.stp, cmdline_args won't return data after the first NULL argument. Version-Release number of selected component (if applicable): systemtap-1.2-9.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. stap cmdlinefail.stp (see attached file) 2. In a separate window, execute: /bin/ls "" additional arguments 3. Look at stap output Actual results: stap displays: /bin/ls Expected results: stap displays: /bin/ls ^@ additional arguments Note, that instead of ^@, it could display something else, or even nothing, but it should display the additional arguments. Additional info: