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.

Bug 1377971

Summary: Expect reduces its output on aarch64.
Product: Red Hat Enterprise Linux 7 Reporter: Matej Habrnal <mhabrnal>
Component: expectAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: bnater, jfeeney, yselkowi
Target Milestone: rc   
Target Release: 7.6   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:46:18 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: 1498541    
Attachments:
Description Flags
Expect reproducer
none
text file needed by expect_reproducer
none
Minimal reproducer none

Description Matej Habrnal 2016-09-21 08:11:01 UTC
Created attachment 1203177 [details]
Expect reproducer

Description of problem:
When I run spawn cat $LONG_TEXT_FILE in expect, expect do not print the whole file but its output is somehow truncated. 

I am attaching reproducer of this issue.

Version-Release number of selected component (if applicable):
expect-5.45-14.el7_1.aarch64

How reproducible:
Always

Steps to Reproduce:
1. run expect_reproducer $ ./expect_reproducer

Actual results:

spawn cat cus.log
core_backtrace: 1
:{   "signal": 11
:,   "executable": "/usr/bin/will_segfault"
:,   "stacktrace":

...

:              , {   "address": 4396484134880
:                ,   "build_id": "42cc8b40c4454279e954617a3217dc37e9d4ed62"
:                ,   "build_id_offset": 2016


Expected results:

spawn cat cus.log
core_backtrace: 1
:{   "signal": 11
:,   "executable": "/usr/bin/will_segfault"
:,   "stacktrace":

...

:        } ]
:}
------- END --------

Comment 1 Matej Habrnal 2016-09-21 08:12:03 UTC
Created attachment 1203178 [details]
text file needed by expect_reproducer

Comment 3 Vitezslav Crhonek 2016-10-24 12:22:27 UTC
Created attachment 1213464 [details]
Minimal reproducer

Comment 4 Vitezslav Crhonek 2016-10-24 12:25:22 UTC
Inserting "sleep 0.1" right after "spawn" command workarounds the issue for me.

Comment 10 RHEL Program Management 2020-12-15 07:46:18 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.