Searched hist:287081 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-11.0-release/bin/sh/tests/errors/ | ||
| H A D | bad-parm-exp7.0 | 287081 Sun Aug 23 20:55:41 MDT 2015 jilles sh: Don't create bad parse result when postponing a bad substitution error. An invalid substitution like ${var@} does not cause a parse error but is stored in the intermediate representation, to be written as part of the error message. If there is a CTL* byte in the stored part, this confuses some code such as the code to skip an unused alternative such as in ${var-alternative}. To keep things simple, do not store CTL* bytes. Found with afl-fuzz. MFC after: 1 week |
| H A D | bad-parm-exp8.0 | 287081 Sun Aug 23 20:55:41 MDT 2015 jilles sh: Don't create bad parse result when postponing a bad substitution error. An invalid substitution like ${var@} does not cause a parse error but is stored in the intermediate representation, to be written as part of the error message. If there is a CTL* byte in the stored part, this confuses some code such as the code to skip an unused alternative such as in ${var-alternative}. To keep things simple, do not store CTL* bytes. Found with afl-fuzz. MFC after: 1 week |
| H A D | Makefile | diff 287081 Sun Aug 23 20:55:41 MDT 2015 jilles sh: Don't create bad parse result when postponing a bad substitution error. An invalid substitution like ${var@} does not cause a parse error but is stored in the intermediate representation, to be written as part of the error message. If there is a CTL* byte in the stored part, this confuses some code such as the code to skip an unused alternative such as in ${var-alternative}. To keep things simple, do not store CTL* bytes. Found with afl-fuzz. MFC after: 1 week |
| /freebsd-11.0-release/bin/sh/ | ||
| H A D | parser.c | diff 287081 Sun Aug 23 20:55:41 MDT 2015 jilles sh: Don't create bad parse result when postponing a bad substitution error. An invalid substitution like ${var@} does not cause a parse error but is stored in the intermediate representation, to be written as part of the error message. If there is a CTL* byte in the stored part, this confuses some code such as the code to skip an unused alternative such as in ${var-alternative}. To keep things simple, do not store CTL* bytes. Found with afl-fuzz. MFC after: 1 week |
Completed in 175 milliseconds