Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685026 - bcc-tools: some scripts do not work
Summary: bcc-tools: some scripts do not work
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: bcc
Version: 8.0
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jerome Marchand
QA Contact: Christian Trautman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 08:09 UTC by Michael Petlan
Modified: 2019-03-07 12:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Michael Petlan 2019-03-04 08:09:33 UTC
Description of problem:

I am sorry I don't have a complete list of tools in bcc-tools with statuses "works" or "does not work", but I have noticed that some scripts do not bring the expected results. This needs deeper testing and investigation probably, so I'll keep updating this bug when having more information.

Version-Release number of selected component (if applicable):
bcc-tools-0.7.0-5.el8

How reproducible:
100%

Steps to Reproduce:
1. cd /usr/share/bcc/tools/
2. ./bashreadline
3. run commands in another shell

Actual results:
The commands are not printed out byt ./bashreadline.

Expected results:
All shell commands are printed, as they are on x86_64.

Additional info:

There are others, like the python*, perl* and similar tools which seem to not work as properly as on x86_64, however I need to test them more.

Comment 1 Michael Petlan 2019-03-06 12:56:01 UTC
Testing on s390x, bashreadline semi-works - it prints timestamp and pid, but not the command:

# ./bashreadline 
TIME      PID    COMMAND
07:46:56  52046  
07:46:57  52046  
07:46:58  52046  
07:46:59  52046  
07:47:04  52046  
07:47:08  52046  
07:47:10  52094  
07:47:12  52046

Comment 2 Michael Petlan 2019-03-07 12:27:31 UTC
The problem with s390x, mentioned in comment #1 (the string is missing), might be probably caused by the s390x design, where it is not possible to easily share string data from kernel to userspace. Thus, it might be expected that bashreadline can't work on s390x.

See:
Thread: https://www.spinics.net/lists/linux-s390/msg23608.html
More here: https://www.spinics.net/lists/linux-s390/msg23612.html


Note You need to log in before you can comment on or make changes to this bug.