Patch-ID: bash32-040 When using the `set' builtin to list all shell variables, the shell uses the wrong variable when computing the length of a variable's value. Patch-ID: bash32-041 Bash saved and restored the value of `set -o history' while sourcing files, preventing users from turning off history with `set +o history' in .bashrc. Patch-ID: bash32-042 An operator precedence error prevented the bash arithmetic evaluator from parsing conditional commands correctly. Patch-ID: bash32-043 Side effects caused by setting function-local versions of variables bash handles specially persisted after the function returned. Patch-ID: bash32-044 The presence of invisible characters in a prompt longer than the screenwidth with invisible characters on the first and last prompt lines caused readline to place the cursor in the wrong physical location. Patch-ID: bash32-045 When short-circuiting execution due to the `break' or `continue' builtins, bash did not preserve the value of $?. Patch-ID: bash32-046 Bash did not compute the length of multibyte characters correctly when performing array element length references (e.g., ${#var[subscript]}). Patch-ID: bash32-047 When using the `.' (source) builtin, under certain circumstances bash was too careful in discarding state to preserve internal consistency. One effect was that assignments to readonly variables would cause entire scripts to be aborted instead of execution of the offending command. This behavior was introduced by bash-3.2 patch 20. Patch-ID: bash32-048 When invoked as `bash -c', bash did not execute an EXIT trap when the last command in the executed list was a command run from the file system. Reproducible: Always
Bumped
