Bug 453123 - [REGRESSION] Wrong input confuses bash's arithmetic unit permanently
[REGRESSION] Wrong input confuses bash's arithmetic unit permanently
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: bash (Show other bugs)
All Linux
high Severity urgent
: rc
: ---
Assigned To: Roman Rakus
Ben Levenson
: Regression
Depends On:
  Show dependency treegraph
Reported: 2008-06-27 09:00 EDT by Enrico Scholz
Modified: 2014-01-12 19:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 16:10:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2008-06-27 09:00:24 EDT
Description of problem:

Bug #286861 affects RHEL 5.2 too:

Scripts like

: $(( tmp=foo.a+0 )) 
i=0 ; : $(( ++i )) ; echo $i 

return the expected '1' on RHEL 5.1, but '0' on RHEL 5.2.  Further arithmetic
operations will be ignored silently.

This breaks existing applications, which check e.g. for numeric input with this

Version-Release number of selected component (if applicable):

bash-3.2-21.el5 (broken)
bash-3.1-16.1   (ok)

How reproducible:

Comment 1 Roman Rakus 2008-06-27 10:10:02 EDT
Patch should be backported.
Comment 2 RHEL Product and Program Management 2008-06-27 10:24:35 EDT
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.
Comment 9 errata-xmlrpc 2009-01-20 16:10:10 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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