| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
This is an upstream bugfix (with slight alterations):
Patch-ID: bash42-053
A combination of nested command substitutions and function importing from
the environment can cause bash to execute code appearing in the environment
variable value following the function definition.
Change-Id: I660e59c76d0d50de52d48a0d399fe1dfef3bded8
|
| |
|
|
|
|
|
|
| |
Patch-ID: bash30-017
Under certain circumstances, bash will execute user code while processing the
environment for exported function definitions.
Change-Id: Iccac7b4ae914354978079783a9fe50b3b38ddad5
|
| |
|
|
|
|
|
| |
This upgrades bash to from 4.1-rc to 4.2-release. See CWRU/changelog for
changes.
Change-Id: I926269c300cf44fa25964b5b375a148fcf11c4b7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In get_working_directory(), the getcwd call in the __ANDROID__
workaround case was obviously wrong, having sizeof(char *) as a length
argument instead of the length of the malloced string itself. Also, no
check for malloc failure was there.
With this fix, tested on maguro, using bash with the usual prompt
containing pwd references, as well as the pwd bash builtin itself,
no longer spew these annoying messages mentioned in the title.
Also made a small change to sh_invalidnum() to fix compile warnings.
Change-Id: I9546e07731a251f80e410935619ddcf0873694af
|
| |
|
|
| |
Change-Id: I7f64112c5449c27b1216c0ddf6a7416b1b011ad6
|
| | |
|
| | |
|
| |
|
