|author||Rich Felker <email@example.com>||2015-03-20 18:06:04 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2015-03-20 18:06:04 -0400|
fix memory-corruption in regcomp with backslash followed by high byte
the regex parser handles the (undefined) case of an unexpected byte following a backslash as a literal. however, instead of correctly decoding a character, it was treating the byte value itself as a character. this was not only semantically unjustified, but turned out to be dangerous on archs where plain char is signed: bytes in the range 252-255 alias the internal codes -4 through -1 used for special types of literal nodes in the AST.
Diffstat (limited to 'src/ipc')
0 files changed, 0 insertions, 0 deletions