On 8/18/15 9:12 AM, Dan Douglas wrote:
> Actually I think I spoke too soon. There's already some considerable logic in
> braces.c to check for overflow (e.g. around braces.c:390 shortly after
> declaration of the int). Looks like there were some changes in this code last
> year to "beef it up" a bit. (see commit
> 67440bc5959a639359bf1dd7d655915bf6e9e7f1). I suspect this is probably fixed
> in
> devel.
Well, `fixed' is a tricky thing. There is code in bash-4.4 to use malloc
instead of xmalloc -- which just aborts on failure -- but there is only so
much you can do to protect someone from himself.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
